biztrac. BETA
COMPANY REGISTER PROFILE
823193262 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

NIPPON RESTAURANTDRIFT AS

Org. no. 823193262 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 12.8m
Operating profit NOK 1.4m
Equity NOK 2.8m
Incorporated 2019
Employees 14
Share capital NOK 30,000

NIPPON RESTAURANTDRIFT AS is registered as a limited company in Drammen, Buskerud with organisation number 823193262. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019 and has 14 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Restaurantdrift, takeout og catering.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 12.8m
▲ +0 %
Operating profit
NOK 1.4m
▼ −41 %
Equity
NOK 2.8m
▲ +64 %
Est. value
NOK 7.4m

Financial health · 2025

Liquidity
2.67
Very good
Current assets ÷ current liabilities
Profitability
36.1%
Very good
Return on total assets
Solidity
62.5%
Very good
Equity as a share of total capital

Who owns NIPPON RESTAURANTDRIFT AS?

NIPPON RESTAURANTDRIFT AS
NOK 12.8m rev. · NOK 1.4m profit

NIPPON RESTAURANTDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NIPPON RESTAURANTDRIFT AS

Who owns NIPPON RESTAURANTDRIFT AS?

Helena Phan is the largest registered owner, with 100.0%.

What is the revenue of NIPPON RESTAURANTDRIFT AS?

NIPPON RESTAURANTDRIFT AS had revenue of NOK 12.8m in 2025.

Who is the general manager of NIPPON RESTAURANTDRIFT AS?

Helena Phan is registered as general manager of NIPPON RESTAURANTDRIFT AS.

Where is NIPPON RESTAURANTDRIFT AS based?

NIPPON RESTAURANTDRIFT AS has its business address in Drammen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.