BIZTRAC BETA
Architectural activities

ATELIER OSLO AS

Org. no. 994734938 Limited company (AS) Oslo Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 23.8m
Operating profit NOK 1.6m
Equity NOK 6.3m
Incorporated 2009
Employees 17
Share capital NOK 100,000

ATELIER OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 994734938. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2009 and has 17 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Arkitektfaglig virksomhet innenfor bygg, prosjektering, prosjektledelse, planlegging, utredning, regulering og undervisning/forskning samt enhver annen for formålet hensiktsmessig virksomhet, herunder deltakelse i andre selskaper med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 23.8m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 23.8m
Operating profit
NOK 1.6m
Equity
NOK 6.3m
Est. value
NOK 11.6m

Financial health · 2025

Liquidity
2.08
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
52.0%
Very good
Equity as a share of total capital

Who owns ATELIER OSLO AS?

NILS OLE BAE BRANDTZÆG
ATELIER OSLO AS
NOK 23.8m rev. · NOK 1.6m profit

ATELIER OSLO AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ATELIER OSLO AS

Who owns ATELIER OSLO AS?

NILS OLE BAE BRANDTZÆG is the largest registered owner, with 25.0%.

What is the revenue of ATELIER OSLO AS?

ATELIER OSLO AS had revenue of NOK 23.8m in 2025.

Who is the general manager of ATELIER OSLO AS?

Jonas Baadstø Norsted is registered as general manager of ATELIER OSLO AS.

Where is ATELIER OSLO AS based?

ATELIER 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.