Nokia only sold 330k Lumia in the US


Recommended Posts

In the run up to the launch of the Nokia Lumia 900 on AT&T, there were multiple reports that the launch would see unprecedented marketing, with even AT&T saying that it would exceed the scope of the original iPhone launch. Nokia executives boldly referred to the Lumia line as the first ?real? Windows Phonedevices and at one point AT&T claimed claimed that Lumia 900 sales hadexceeded their expectations.

It?s not clear exactly how low Nokia?s expectations were, but a close analysis of the latest Nielsen and comScore numbers shows that Nokia has sold well below half a million Windows phone devices in the U.S. ? they number crunchers at Aymco peg the number at a mere 330,000. And those numbers aren?t just Lumia 900 sales, they are the total sales of all Nokia Windows Phone devices, including the value priced Lumia 710 on T-Mobile (which has been selling for "free" on contract for months) and launched back in January.

How did Asymco derive those numbers? Nielsen and comScore gave them to us: in the breakdown of hardware vendors Nielsen shows Nokia as behind Samsung and HTC?s Windows Phone offerings (despite not being ?real? WP7 devices?) as having made 0.3% of all current U.S. smartphones. Multiple that against the total number of US smartphone owners (which comScore?s recently recorded as 110 million) and you get this:

110,000,000 X 0.003 = 330,000 units.

That is an astonishingly small number, and explains why Windows Phone market share still lags behind even Windows Mobile, over a year and a half after WP7 launched. With Windows Phone 8 coming in a few more months and no upgrade path for current devices to the next version of the software, surely whatever chance at serious market disruption was available is now gone. For Nokia, who bet their company on the success of Windows Phone, WP8 surely cant? come soon enough. And if that doesn?t do the trick, their recently reported back up plan had better be ready for action.

Screen-Shot-2012-07-13-at-10.20.23-AM.png

http://www.phonearen...-the-US_id32257

Yeah, it's pretty obvious by now that nobody gives a **** about Windows Phone. At least not Windows Phone 7. Unless Microsoft/Nokia ramp up the marketing close to Windows 8's launch, it will be the same sad story all over again. Microsoft need to do something FAST.

Microsoft need to do something FAST.

They are, by taking it's hugely successful desktop OS and making it similar as the mobile platform in Windows 8. If it's a success, their desktop OS will pull mobile sales up. If it's a failure, not only will the mobile platform still be a huge antisuccess, but it will also bring down the desktop sales. If the latter happens, it will not be fun for Microsoft.

  • Like 1

Not sure I agree with the numbers 0.3 then 0.003 doesn't make sense to me.

Nokia really do produce some great hardware, simply crippled by their choice of partner. If nothing else try a few Android devices and see how you go.

At this point, they are just waiting for the Windows 8 bump and the WP8 goodies.

There was a post a few days ago saying Nokia has cut Lumia orders, they're going to jump right to WP8. Whatever they've built to date is probably it for now.

I think Nokia needs to do something fast.. like dump Microsoft and Windows Phone and go with Android if they don't want to go the path of RIM.

They definitely need to fire Elop ASAP and make a big marketing push to regain consumer confidence and make it sound like the Nokia going forward is the Nokia that existed pre-Elop and that the Elop Nokia is all just a bad dream. Switching platforms would be a great way to do it, but with the right marketing they might be able to keep Windows Phone and at least stay in business. I don't think there's anyway they recover without distancing themselves from Elop. Even if Windows Phone become a hit or they switch to Android, the combined Osbourning and Ratnering that Elop pulled has poisoned the brand as long as he is attached to it.

Not sure I agree with the numbers 0.3 then 0.003 doesn't make sense to me.

The first is a percent and the second is used in a calculation to determine the percentage so it is the percent divided by 100. For example if you were to get 1% of $100 you wouldn't multiply $100 by 1, you'd multiply it by 0.01

  • Like 1

God please no.

You would rather they just went bankrupt instead? - Nokia can't survive on this small volume of sales and their feature phones in other markets don't make anywhere near enough profit to sustain the company. Why do you think they've just announced in June that a further 10,000 employees will lose their jobs?

Windows Phone is killing them, not enough people are buying them.

The first is a percent and the second is used in a calculation to determine the percentage so it is the percent divided by 100. For example if you were to get 1% of $100 you wouldn't multiply $100 by 1, you'd multiply it by 0.01

And that is why I never became an accountant :) thanks understand it now.

They are, by taking it's hugely successful desktop OS and making it similar as the mobile platform in Windows 8. If it's a success, their desktop OS will pull mobile sales up. If it's a failure, not only will the mobile platform still be a huge antisuccess, but it will also bring down the desktop sales. If the latter happens, it will not be fun for Microsoft.

Unfortunitly I can see that happening for Microsoft...

My sister has a Lumia 710 and I love playing with that, but for the desktop, I personally think the metro interface simply doesn't work well enough for the everyday desktop user.

I think Nokia needs to do something fast.. like dump Microsoft and Windows Phone and go with Android if they don't want to go the path of RIM.

I know I'd buy in a second Nokia Lumia 900 styled Android phone.

Once Windows 8 takes off around the world, Nokia will be laughing.

Trying to enter an already over competitive Android market will bankrupt them.

Guys at Nokia should have chosen Meego instead like so many of us were advocating but instead they got in bed with Microsoft - they aren't the first company to die from association and won't be the last.

?he funny thing is, the N9 was a hit phone, yet it was killed by Nokia and Elop. They didn't even give Meego a chance. Which is a shame, because Tizen, its new form, could become the third ecosystem.

As far as the article is concerned, if those numbers are right, all I'll say is - artificially low stock to create false reports of *selling out*. ?ecause that's what happened, both with the Lumia launch and WP7 as well. Who's going to believe Microsoft or Nokia again when they say they've *sold out* ?

Europeans do. Marketshare is rising but Nokia was always more successful here.

Source? From what I hear in the UK, the Lumia is doing terrible and the operators have criticised WP7 for its inability to compete against iOS and Android.

Nokia is losing marketshare dramatically in Europe now that Symbian is a dead end.

  • Like 1

Once Windows 8 takes off around the world, Nokia will be laughing.

People said the same about WP7. The only ones laughing are those that said Nokia were making a mistake.

Trying to enter an already over competitive Android market will bankrupt them.

Subjective, based purely on opinion, not fact. Nokia can make great hardware, they just need an OS to go with it. WP has not been that OS so far.

AT&T must not be selling any phones then, considering it was the 2nd best seller at AT&T from April to June. I don't know if this is worse news for Nokia or AT&T....

Oh, and don't forget that AT&T and T-mobile are the only carriers with Lumia devices. If they were on Verizon, Sprint, and the other smaller carriers, those numbers would double or triple. Just wait til WP8.

330,000 seems awfully low.

Yea. It seems to be very low. The phone hardware is real nice looking, and I would of thought that consumers unaware of mobile platforms and want a cheap phone would have bought these. This number is what I would of come up with only for Microsoft fans.

Edit: I don't know if it is cheaper than others ....

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • When I think about a network, there are really two aspects, the hardware and the wiring. So here is what I would do for both. Wiring: Use Cat6A for the patch panel and all structured cables (cables installed in walls). Run plenty of Wireless Access Point (WAP) cables, as a general rule, assume a signal can only pass through 2-3 walls and can't pass through a floor (that is conservative, but trust me on this if you want strong WiFi)  Cat6 patch cables are fine for now if you don't plan to run 10gig, those are easy to replace later if needed. Run OS2 single-mode fiber to anywhere you think you may have a server or sub-switch. (yes, single-mode for everything on a small network, don't mess with multimode unless you have entire racks of servers and that minor module cost and power savings will matter). If you really want to future proof, also run fiber to any high density WAP locations, it is likely that WiFi 8 WAPs will push the limits of 10g. Run 6-12 pairs of single-mode fiber between your MDF and the building's MDF, even if you only need 1 or 2 pairs now, those extra pairs will pay off down the road. Hardware: (its easy to say "get all the features incase you need them", so instead of futureproofing, I am going to take approach of suggesting areas worth investing in, and areas you can save money). Don't overspend thinking you need every feature on every port. You don't need 10g on every port, you don't need PoE on every port. Don't overspend on redundancy either, unless you are ready to buy two of everything, don't waste money buying two of some things and not others. Dual power supplies are worthwhile, but probably not HA or multi-path redundancy.  Get 1 "distribution layer" switch that your router/firewall will connect to, your access layer switches. This should be a 10g switch with a combination of copper and SPF ports and should be a fully managed switch. Given that you said it is a small network, I suggest also using that distribution layer switch for servers and WAPs, meaning it will need PoE. Speaking of wireless, get good professional tri-band WAPs, and either turn on the band stirring options, or limit 2.4 to an IoT only SSID. This will provide a solid WiFi capable nearly everything but the highest of bandwidth clients...you could even consider skipping wiring workstations depending on usage. Access layer switch for workstations and printers can be cheaper switches, 2.5g is a good sweet spot between price and future proofing, but even 1g is fine for most individual clients (the kind that could probably be fine on WiFi). You can consider saving a little on access layer switches by only getting 1 PoE switch for whatever needs it (remember your WAPs are connecting to the distribution switch, not here), and non-PoE for your workstations, because desk phones are falling out of favor. You can also save money here by not buying managed switches if you don't need them--but really do some soul searching there, if you go this route, then anything that isn't on your workstation VLAN would either need to be connected to the distribution switch, or its own switch. Also, don't feel like you need a fancy fabric stacking switches for your access layer, that is the point of the higher-end distribution layer, to remove the need for things like that at this level. Home Hardware: I'm realizing the above assumed an office setting, if this if for your house and home lab then the above still applies, but you'll probably want everything managed and PoE, just because, but you probably also don't need multiple access layer switches. if your total port count is below 24, just skip separating distribution layer and access layer and just get one nice switch with the features you want. For home use, don't worry about home running every device to the main switch, there is nothing wrong with running sub-switches for your media areas and office, those essentially become your access layer, just look for sub-switches with a 10g uplink so sharing bandwidth isn't an issue.
    • Google Meet brings Gemini note-taking to AI Pro and Ultra subscribers by Karthik Mudaliar Google's Gemini-powered "Take notes for me" feature inside Google Meet is now available to Google AI Pro and Ultra subscribers. The features work on Google Meet for web as well as on mobile, and Google says that subscribers can use it for meetings they host in many supported languages. As the name suggests, "Take notes for me" allows Gemini to listen to a meeting, generate a summary, identify action items, and save the notes as a Google Doc in the user’s Drive. After the meeting, the organizer receives an email recap with the summary and action items, while the notes can also be attached to the related Calendar event depending on the meeting setup and sharing settings. The feature isn't automatically turned on for everyone, though. Google says that all meeting participants are notified when note-taking is turned on, and users can start it from the pencil icon in Meet or enable it for future calls through Meet’s meeting records settings. For work or school accounts, administrators can also control whether the feature is available and may require explicit participant consent for note-taking, recording, or transcription features. The feature first launched back in 2024, when it was available just for selected Workspace users. Over the years, Google added refinements and more options, including the ability to enable it when scheduling meetings via Google Calendar. Google's support docs say that the feature currently supports English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish, but only one language at a time. Meetings with multiple spoken languages are not currently supported, and Google recommends using the tool for meetings between 15 minutes and eight hours. The new feature makes Google Meet closer to its rivals that have AI tools already built in. Microsoft Teams has recently started offering Copilot and intelligent recap features that summarize meetings, surface highlights, and help with follow-ups, while Zoom’s AI Companion can also generate meeting summaries from desktop and mobile meetings.
    • GnuCash 5.16 by Razvan Serea GnuCash is a personal and small business finance application, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows. It’s designed to be easy to use, yet powerful and flexible. GnuCash allows you to track your income and expenses, reconcile bank accounts, monitor stock portfolios and manage your small business finances. It is based on professional accounting principles to ensure balanced books and accurate reports. GnuCash can keep track of your personal finances in as much detail as you prefer. If you are just starting out, use GnuCash to keep track of your checkbook. You may then decide to track cash as well as credit card purchases to better determine where your money is being spent. When you start investing, you can use GnuCash to help monitor your portfolio. Buying a vehicle or a home? GnuCash will help you plan the investment and track loan payments. If your financial records span the globe, GnuCash provides all the multiple-currency support you need. Between 5.15 and 5.16, the following bugfixes were accomplished: Bug 421610 - RFE: Include logical dates for View->Filter by "date range"The Select Range section of the Date tab of the register's Filter By dialog box is changed to provide relative, specific date, or days ago options for the start and end of the filter range. The Show number of days item label is changed to Show from days ago to better reflect what it does. Bug 436105 - esc key not working as expected in register: Enable the escape key to cancel a field edit. Bug 797384 - Gnucash doesn't handle commodity prices with big numerator/denominator properly. Bug 798004 - Next gen UI for stock transactions Bug 799314 - Add "enter now" option in scheduled transaction editor. tab to allow users to select the scheduled transactions to be included in a “Since Last Run…” window. If there are no instances of a selected transaction triggered by today’s date, the next instance is triggered. Bug 799751 - autocomplete crash Bug 799759 - Users can't Enable entries via Checkboxes on Scheduled Transactions PageAllow the Enabled box in the list of scheduled transactions to be operated instead of having to open the transaction editor dialog and change the Enabled checkbox. Also added use of the Name column as the secondary column sort for all the other columns. Bug 799762 - Poor handling of cases where hidden/placeholder accounts are used in the account register Bug 799766 - Double line preference not respected in search register Bug 799767 - POST /accounts in bindings/python/example_scripts/rest-api is broken Bug 799777 - `xaccSplitSetParent`: reparenting a committed split silently drops its KVP slots (online_id, cap-gains links) Other changes & improvements: Numeric values may now be selected to copy in the Accounts page. Add new Finance::Quote source Finnhub.io: Free API key (personal/non-professional use) available at https://finnhub.io. Set FINNHUB_API_KEY environment variable to API key to use this source. As of June 2026, free tier API limit is 60 API calls/minute. The Investment Lots report has new optional columns for Computed Annual Growth Rate. Python Bindings: Improved translation of primary object (Account, Transaction, Split, etc.) so that they can be treated as normal Python objects. This is accomplished with SWIG magic so no existing code is obsoleted. Python Bindings: Better conversion of GLists to Python lists. Python Bindings: Destroy the QofSession in the Python Session dtor to prevent leaving the database locked. [engine] Add first-class online_id accessors for Split and Account and make them available to Python bindings, removing the unused Transaction online_id property. Improve C++ implementation of QofBook. Correct the Doxygen doc for qof_instance_get/set_kvp. [gnc-log-replay.cpp] fix incorrect guid dump Add some Boost library requirements needed by libgnucash-guile to CMakeLists.txt so that missing feature will fail at configure time. Use Compile-time Regular Expressions instead of std::regex in gnc-filepath-utils.cpp and instead of boost::regex in the CSV importer, with the CTRE v3.11.1 header added to borrowed [gnc-filepath-utils.cpp] null check char* arguments Add ChartJS licenses. Removed AEX from list of commodities. euronext.com is now using JS based anti-webscraping. [report-core] always offer options summary in reports. This is useful to debug reports. The Add options summary option is removed because it's no longer optional. Remove remaining obsolete IMContext from sheet Fix blurry text in HiDPI offscreen-rendered widgets Add port field to database connection dialog: The convention of appending the port number after the host isn't obvious. When editing a split in the register treat the account as being changed only if it isn't the one selected before editing instead of if the user performed an edit Return immediately from qof_book_destroy if hash_of_collections is null. If qof_book_destroy is called on a QofBook* freshly created with qof_book_new (usually because it was used to create a session that now must be destroyed) it would try to empty the non-existent hash tables, crashing. Clean up Flathub metadata to solve warnings at flatpak build time. Be consistent in naming GncPluginPage and GncPluginPageRegister HTML: Remove unimplemented function declarations. [gnc-html.cpp] remove unused buggy string conversion functions Convert libgnc-html to C++ Apply -Wall -Werr -Wmissing-prototypes to C++ compilation on Windows and fix the resulting errors. New and Updated Translations: Arabic, Croatian, Danish, Dutch, German, Finnish, Hungarian, Korean, Norwegian-Bokmal, Spanish Download: GnuCash 5.16 | 176.0 MB (Open Source) Links: GnuCash Home page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally launches WSL Containers in public preview by David Uzondu Microsoft has announced that WSL containers, a feature that allows developers to run Linux containers natively inside Windows without the need for Docker Desktop, is now available in public preview several weeks after Microsoft previewed it at Build 2026. To use the new container feature, you first have to install the latest pre-release version of the Windows Subsystem for Linux by running a quick update command in your terminal: wsl --update --pre-release After installing, you'd get access to the new Linux container CLI (wslc.exe) and the programmable API. Microsoft said that the CLI has a "familiar format" that matches the toolsets developers already use every day. If you know standard Docker commands, your muscle memory will translate directly to wslc.exe, which even features a built-in alias called container.exe. You can quickly run a full Ubuntu KDE desktop container by exposing ports, or pass your graphics card straight into a machine learning environment to run PyTorch workloads. Passing the --gpus all flag inside the run command instantly links your hardware. Image via Microsoft As for the API, developers can now embed Linux container operations directly inside native Windows applications without exposing the command line to users. The team integrated the API directly into MSBuild and CMake, so developers can define container steps directly in project files. Apart from bringing the CLI and API into public preview, Microsoft also said that it's working on a new default file system called virtiofs to speed up file transfer rates between Windows and Linux. Microsoft also introduced an experimental networking mode named consomme, which resolves compatibility issues with corporate VPNs by routing Linux network traffic straight through Windows. One thing to note about WSL containers is that they don't run in your standard WSL distributions; instead, every application and CLI session spawns its own lightweight Hyper-V utility VM in the background. This basically reduces the chances of one app snooping on the container of another app.
    • Google reportedly limited Meta's Gemini access over limited AI compute by Karthik Mudaliar Google is reportedly limiting Meta's use of its Gemini AI models after Meta tried buying more computing capacity than even Google could supply. According to the Financial Times, Google told Meta in March that it could not provide the full Gemini capacity that Meta had requested. This shortfall even disrupted and delayed some of Meta's internal projects. Due to this, Meta even told its employees internally to use AI tokens more efficiently. Meta wasn't the only one to get hit by this sudden refusal by Google; even other customers were affected. But Meta was hit harder because of its unusually high demand for Google's models. The move from Google makes it evident that companies all over are in limited supply of both infrastructure and compute. Alphabet said in April that Google Cloud revenue grew 63% year-over-year to $20 billion in the first quarter, helped by enterprise AI infrastructure and AI solutions. In pursuit of more compute, Meta had earlier signed a multi-billion-dollar AWS agreement as well as a large AMD GPU deal for AI data centers. But the crunch would be short-lived as both Meta and Google have also ramped up infrastructure investments heavily. Meta said in November that it was committing more than $600 billion in the U.S. by 2028 for AI technology, infrastructure, and workforce expansion. In the first quarter of this year, Meta also raised its expected capital expenditure for 2026 to a range of $125 billion to $145 billion, citing higher component pricing and additional data center costs for future capacity. However, this doesn't make the company immune to the current dependence on outside suppliers. Meta has also spent many years promoting Llama as an open-weight alternative to closed models from Google, OpenAI, and Anthropic. But if the reported reliance on Google's Gemini models is severe enough for internal work to get impacted, then it looks like even frontier labs and Big Tech aren't fully self-sufficient. Source: Financial Times
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      533
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!