Today following the bell, Google reported its third quarter earnings: The company had gross revenue of $16.52 billion, revenue net of traffic acquisition costs (ex-TAC) of $13.17 billion, GAAP earnings per share of $4.09, and non-GAAP earnings per share of $6.35.
Analysts had expected Google to earn $6.53 per share on a non-GAAP basis, on net ex-TAC revenue of $13.22 billion. In the sequentially preceding quarter, Google earned $6.08 in non-GAAP earnings per share, on ex-TAC revenue of $12.67 billion.
Google fell more than 1 percent in regular trading. In after-hours, following its mixed earnings report, the company is down more than 3 percent. (Update: Google, off more than 5 percent at one point, is now down a more modest 2 percent.)
Google is working to expand its revenue base away from advertising. It is currently locked in the intertwined productivity-storage-cloud computing wars with Amazon, Microsoft, Box, Dropbox, Egnyte, Apple, HighQ and others. Declining prices in that space have lowered short-term revenue potential, but that fact has done what I estimate to be a grand total of zero to lower competitive tension in the market area.
The company reported net income of $3.72 billion in the period.
Breaking down Google’s revenue by segment, you have the following:
- Sites Revenue: $11.25 billion. Up 20 percent from the preceding year’s quarter.
- Network Revenue: $3.43 billion. Up 9 percent from the preceding year’s quarter.
- International revenue: 58 percent of revenue. Up 2 percent from the preceding year’s quarter.
The company reported that its average cost-per-click fell 2 percent in the period, a weakening in a key revenue source. However, pushing back against that decline was a 17 percent year-over-year increase in ‘aggregate paid clicks.’ So, while the amount of revenue that Google managed to extract from a click went down mildly, it sold more than one sixth more then compared to the year-ago quarter.
We’re updating, hit refresh.
from TechCrunch http://feedproxy.google.com/~r/Techcrunch/~3/tSZ6Y_nNO0s/
via IFTTT
0 comments:
Post a Comment