News Release zvws090805c

5. Average Monthly Revenue per Unit (ARPU)

Average monthly revenue per unit, or ARPU, is used to measure average monthly operating revenues attributable to designated services on a per user basis. In the case of our fixed line business, ARPU is calculated by dividing revenue items included in the operating revenues of our Regional Communications Business, that is, telephone subscriber lines, INS-NET and FLET'S Hikari, by the number of active subscribers to the relevant services.
In the case of our mobile business, ARPU is calculated by dividing revenue items included in the operating revenues from our Mobile Communications Business, such as revenues from Mobile (FOMA) services and revenues from Mobile (mova) services, which are incurred consistently each month (i.e., basic monthly charges and voice/packet transmission charges), by the number of active subscribers to the relevant services. The calculation of these figures excludes revenues that are not representative of monthly average usage such as equipment sales, activation fees and universal service charges.
We believe that our ARPU figures calculated in this way provide useful information regarding the monthly average usage of our subscribers. The revenue items included in the numerators of our ARPU figures are based on our financial results comprising our U.S. GAAP results of operations.

5. Average Monthly Revenue per Unit (ARPU)

*	Partial listing only

Notes :

We separately compute the following four categories of ARPU for the fixed line business conducted by each of NTT East and NTT West, using the following measures:

Aggregate Fixed Line ARPU (Telephone Subscriber Lines + INS-NET Subscriber Lines): Calculated based on revenues from monthly charges and call charges for Telephone Subscriber Lines and INS-NET Subscriber Lines, which are included in operating revenues from Voice Transmission Services (excluding IP Services), and revenues from FLET'S ADSL and FLET'S ISDN, which are included in operating revenues from IP Services.

Telephone Subscriber Lines ARPU: Calculated based on revenues from monthly charges and call charges for Telephone Subscriber Lines and revenues from FLET'S ADSL.

INS-NET Subscriber Lines ARPU: Calculated based on revenues from monthly charges and call charges for INS-NET Subscriber Lines and revenues from FLET'S ISDN.

FLET'S Hikari ARPU: Calculated based on revenues from FLET'S Hikari (including FLET'S Hikari optional services), which are included in operating revenues from IP Services and Supplementary Business, and revenues from monthly charges, call charges and device connection charges for Hikari Phone, which are included in operating revenues from IP Services.

FLET'S Hikari includes B FLET'S and FLET'S Hikari Next (launched on Mar. 31, 2008) provided by NTT East, and B FLET'S, FLET'S Hikari Premium, FLET'S Hikari Mytown and FLET'S Hikari Next (launched on Mar. 31, 2008) provided by NTT West.

Commencing in the fiscal year ending Mar. 31, 2010, NTT East and NTT West have begun including in their FLET'S Hikari ARPU calculation revenues from the "Remote Support Service", a FLET'S Hikari's optional service, which are part of their operating revenues from Supplementary Business.Accordingly, calculations for NTT East and NTT West's FLET'S Hikari ARPU for the three months ended Jun. 30, 2008, Sep. 30, 2008, Dec. 31, 2008 and Mar. 31, 2009, and the fiscal year ended Mar. 31, 2009 include revenues from Remote Support Service.
Revenues from NTT East's Remote Support Service contributed, respectively, 10 yen, 20 yen, 20 yen, 40 yen, 30 yen and 50 yen to NTT East's FLET'S Hikari ARPU for the three months ended Jun. 30, 2008, Sep. 30, 2008, Dec. 31, 2008 and Mar. 31, 2009, the fiscal year ended Mar. 31, 2009, and the three months ended Jun. 30, 2009 (representing, respectively, 0.2%, 0.4%, 0.4%, 0.7%, 0.5% and 0.9% of NTT East's total FLET'S Hikari ARPU for the same periods). Revenues from NTT East's Remote Support Service contributed 60 yen to NTT East's forecast FLET'S Hikari ARPU for the fiscal year ending Mar. 31, 2010 (representing 1.0% of NTT East's total FLET'S Hikari ARPU for the same period).
Revenues from NTT West's Remote Support Service contributed, respectively, 0 yen, 0 yen, 0 yen, 0 yen, 0 yen and 0 yen to NTT West's FLET'S Hikari ARPU for the three months ended Jun. 30, 2008, Sep. 30, 2008, Dec. 31, 2008 and Mar. 31, 2009, the fiscal year ended Mar. 31, 2009, and the three months ended Jun. 30, 2009 (representing, respectively, 0%, 0%, 0%, 0%, 0% and 0% of NTT West's total FLET'S Hikari ARPU for the same periods). Revenues from NTT West's Remote Support Service contributed 30 yen to NTT West's forecast FLET'S Hikari ARPU for the fiscal year ending Mar. 31, 2010 (representing 0.5% of NTT West's total FLET'S Hikari ARPU for the same period).

Revenues from interconnection charges are excluded from the calculation of Aggregate Fixed Line ARPU (Telephone Subscriber Lines + INS-NET Subscriber Lines), Telephone Subscriber Lines ARPU, INS-NET Subscriber Lines ARPU, and FLET'S Hikari ARPU.

For purposes of calculating Aggregate Fixed Line ARPU (Telephone Subscriber Lines + INS-NET Subscriber Lines), Telephone Subscriber Lines ARPU and INS-NET Subscriber Lines ARPU, the number of subscribers is determined using the number of lines for each service.

In terms of number of channels, transmission rate, and line use rate (base rate), INS-Net 1500 is in all cases roughly ten times greater than INS-Net 64. For this reason, one INS-Net 1500 subscription is calculated as ten INS-Net 64 subscriptions.

For purposes of calculating FLET'S Hikari ARPU, number of subscribers is determined based on number of FLET'S Hikari subscribers including B FLET'S and FLET'S Hikari Next (launched on Mar. 31, 2008) provided by NTT East and B FLET'S, FLET'S Hikari Premium, FLET'S Hikari Mytown and FLET'S Hikari Next (launched on Mar. 31, 2008) provided by NTT West.

We compute ARPU for our mobile business using three aggregate measures.

-	Mobile Aggregate ARPU (FOMA+mova) = Voice ARPU (FOMA+mova) + Packet ARPU (FOMA+mova).
	-	Our Voice ARPU (FOMA+mova) is based on operating revenues related to voice services, such as basic monthly charges and voice transmission charges, attributable to our third generation FOMA and conventional mova services, and our Packet ARPU (FOMA+mova) is based on operating revenues related to packet communication services, such as basic monthly charges and packet transmission charges, attributable to our third generation FOMA services and based on operating revenues related to i-mode services, such as basic monthly charges and packet transmission charges, attributable to our conventional mova services. We also separately compute i-mode ARPU (FOMA+mova), as a subcomponent of Packet ARPU (FOMA+mova). i-mode ARPU (FOMA+mova) is based on operating revenues from basic monthly charges and packet transmission charges attributable to our i-mode-related FOMA and mova services.
-	Mobile Aggregate ARPU (FOMA) = Voice ARPU (FOMA) + Packet ARPU (FOMA).
	-	Our Voice ARPU (FOMA) is based on operating revenues related to voice services, such as basic monthly charges and voice transmission charges, and our Packet ARPU (FOMA) is based on operating revenues related to packet communication services, such as basic monthly charges and packet transmission charges, in each case attributable to our third generation FOMA services. We also separately compute i-mode ARPU (FOMA), as a subcomponent of Packet ARPU (FOMA). i-mode ARPU (FOMA) is based on operating revenues from basic monthly charges and packet transmission charges attributable to our i-mode-related FOMA services.
-	Mobile Aggregate ARPU (mova) = Mobile Voice ARPU (mova) + i-mode ARPU (mova).
	-	Our Voice ARPU (mova) is based on operating revenues related to voice services, such as basic monthly charges and voice transmission charges, and our i-mode ARPU (mova) is based on operating revenues related to i-mode services, such as basic monthly charges and packet transmission charges, in each case attributable to our conventional mova services.

We show ARPU for our i-mode using two aggregate measures.

-	i-mode ARPU (FOMA+mova, FOMA and mova) is based on the number of all subscribers who have active mobile phones, regardless of whether the i-mode service is activated.
-	ARPU generated purely from i-mode (FOMA+mova, FOMA and mova) is based on the number of active subscribers to the i-mode service only.

Communications module service subscribers and the revenues therefrom are not included in the calculations of Mobile Aggregate ARPU.

Number of active subscribers used in the ARPU calculation of NTT East and NTT West are as below.

-	1Q Results: Sum of number of active subscribers**(as defined below) for each month from Apr. to Jun.
-	2Q Results: Sum of number of active subscribers** for each month from Jul. to Sept.
-	3Q Results: Sum of number of active subscribers** for each month from Oct. to Dec.
-	4Q Results: Sum of number of active subscribers** for each month from Jan. to Mar.
-	FY Results : Sum of number of active subscribers** for each month from Apr. to Mar.
-	FY Forecast : the average expected active number of subscribers (number of subscribers at end of previous Mar. + number of expected subscribers at end of the following Mar.)/2x12

Number of active subscribers used in the ARPU calculation of NTT DOCOMO are as below.

1Q Results: Sum of number of active subscribers**(as defined below) for each month from Apr. to Jun.

2Q Results: Sum of number of active subscribers** for each month from Jul. to Sept.

3Q Results: Sum of number of active subscribers** for each month from Oct. to Dec.

4Q Results: Sum of number of active subscribers** for each month from Jan. to Mar.

FY Results: Sum of number of active subscribers** for each month from Apr. to Mar.

FY Forecast: Sum of expected number of active subscribers** for each month from Apr. ro Mar.

**	active subscribers = (number of subscribers at end of previous month + number of subscribers at end of the current month)/2