BIZTRAC BETA
Retail sale of bread, cake and confectionery

STADION BAKERI AS

Org. no. 996531937 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 13.0m
Operating profit NOK 313,000
Equity NOK 1.9m
Incorporated 2011
Employees 17
Share capital NOK 100,000

STADION BAKERI AS is registered as a limited company in Oslo, Oslo with organisation number 996531937. The business is classified under retail sale of bread, cake and confectionery (NACE 47.240). The company was incorporated in 2011 and has 17 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av kafe/bakeriutsalg, samt alt som naturlig hører sammen med dette, herunder deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.0m in revenue and NOK 313,000 in operating profit.

Key figures · 2025

Revenue
NOK 13.0m
Operating profit
NOK 313,000
Equity
NOK 1.9m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns STADION BAKERI AS?

BØR & NOR AS
STADION BAKERI AS
NOK 13.0m rev. · NOK 313,000 profit

STADION BAKERI AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STADION BAKERI AS er morselskap for 1 datterselskap:

Frequently asked questions about STADION BAKERI AS

Who owns STADION BAKERI AS?

BØR & NOR AS is the largest registered owner, with 100.0%.

What is the revenue of STADION BAKERI AS?

STADION BAKERI AS had revenue of NOK 13.0m in 2025.

Who is the general manager of STADION BAKERI AS?

Erik Nordbrenden is registered as general manager of STADION BAKERI AS.

Where is STADION BAKERI AS based?

STADION BAKERI 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.