Adjusted EBITDA was $0.7 million for Q3 2012 compared to $0.4 million for Q2 2012. IPass reported a GAAP net loss of $0.8 million for Q3 2012 compared to a GAAP net loss of $0.9 million for Q2 2012. IPass reported revenues of $30.8 million for Q3 2012 compared to $32.2 million for Q2 2012.
Ipass call free#
"As we head into the fourth quarter, we continue to focus on driving value for our stockholders and are on track to deliver on our commitment of positive adjusted EBITDA and free cash flow generation for the full-year 2012." "We delivered a solid quarter of positive adjusted EBITDA and positive free cash flow as the economic flywheel of Open Mobile begins to take hold," said Steven Gatoff, senior vice president and CFO of iPass. "The global demand for Wi-Fi roaming continues to gain momentum and importance with carriers and subscribers worldwide and we're seeing solid adoption of our unique OMX Wi-Fi roaming platform." We've reached an important milestone where more than 60% of the iPass platform revenue and more than one-third of our Wi-Fi network revenue are now driven by Open Mobile with visibility for Wi-Fi revenue to grow again in total," said Evan Kaplan, president and CEO of iPass. "We're pleased to see things moving in the right direction across a number of fronts with our core Open Mobile platform and global Wi-Fi businesses as we delivered another quarter of strong user growth and customer wins. ( NASDAQ: IPAS), the global Wi-Fi roaming leader for enterprises and telecom service providers, today announced financial results for the third quarter ended September 30, 2012. For details on the current values that may appear in this field, please click here.REDWOOD SHORES, CA-(Marketwire - Nov 7, 2012) - iPass Inc. This field details how the call was rated, and is a character field of up to 32 ASCII characters. The current values for this field are DIAL, ENET and WIFI. This field describes the type of technology used to access the network, and is a character field of up to 32 characters. This numeric field contains the total cost for the transaction (before any applicable discount is applied). This numeric field provides the contracted rate for use of the access point.
All billing occurs of the GMT Time, Local Time is for informational purposes only.Ī numeric field indicating the number of seconds that the user was connected. The value is the result of iPass applying a stored offset for the location to the GMT Time. It is a fixed length character string with format “DD-MON-YYYY hh24:mm:ss”. This field contains the local time of the connection at the provider. This is a fixed length character string with format “DD-MON-YYYY hh24:mm:ss”. It is the time used by iPass for internal processing purposes such as determining which month a transaction occurred in. This timestamp is in Greenwich Mean Time (GMT) and records when the transaction was completed (i.e., transaction stop time).
Ipass call iso#
Special usage refers to keywords which indicate other relevant usage parameters, such as the use of toll free numbers (appears as 'Tollfree-ZZ', where ZZ is the two letter ISO country code), or high speed broadband access (appears as BrdBnd). This field allows you to include a location description on your own statements. The format is the ISO country code, city and venue name, special usage, and state. This is a character field of up to 80 ASCII characters. This field typically contains a description of the location at which the service was provided. The length of this field can be up to 128 ASCII characters. It is normally identical to the corporate authentication domain, but may be different if an over-qualified domain name is used (e.g., instead of ). This is the authentication domain specified by the user when connecting. The length of this field can be up to 256 ASCII characters. It is a character field of up to 32 ASCII characters. It may be used for matching transaction records with other reports, and for identifying transactions when investigating problems. This field contains a unique identifier for each transaction.
0 kommentar(er)
