BIZTRAC BETA
Business and other management consultancy activities

GREATER OSLO AS

Org. no. 911785331 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 51,000
Equity NOK 32,000
Incorporated 2013
Share capital NOK 30,000

GREATER OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 911785331. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Skal gjøre Oslo til en av verdens mest attraktive byer for talenter, selskaper og investorer. Ved å se næringsutvikling og byutvikling i sammenheng skal vi ta Oslo til verden og verden til Oslo.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 51,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 51,000
Equity
NOK 32,000
Est. value
NOK 272,000

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GREATER OSLO AS?

ERLING FOSSEN
GREATER OSLO AS
NOK 1.3m rev. · NOK 51,000 profit

GREATER OSLO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GREATER OSLO AS

Who owns GREATER OSLO AS?

ERLING FOSSEN is the largest registered owner, with 100.0%.

What is the revenue of GREATER OSLO AS?

GREATER OSLO AS had revenue of NOK 1.3m in 2025.

Who is the general manager of GREATER OSLO AS?

Erling Fossen is registered as general manager of GREATER OSLO AS.

Where is GREATER OSLO AS based?

GREATER OSLO AS has its business address in Oslo.

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

Report a problem

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