BIZTRAC BETA
Rental and operating of own or leased real estate

AXEL BIRK AS

Org. no. 998629020 Limited company (AS) Østre Toten Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 23,000
Incorporated 2012
Share capital NOK 30,000

AXEL BIRK AS is registered as a limited company in Østre Toten, Innlandet with organisation number 998629020. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eierinteresse i andre AS, samt fast eiendom. Kjøp/salg av varer og tjenester. Selskapet kan også delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 23,000
Est. value
NOK 21,000

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.1%
Weak
Equity as a share of total capital

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

Who owns AXEL BIRK AS?

AXEL BIRK
AXEL BIRK AS
NOK 0 rev. · NOK 0 profit

AXEL BIRK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AXEL BIRK AS own?

AXEL BIRK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AXEL BIRK AS

Who owns AXEL BIRK AS?

AXEL BIRK is the largest registered owner, with 100.0%.

What is the revenue of AXEL BIRK AS?

AXEL BIRK AS had revenue of NOK 0 in 2025.

Who is the general manager of AXEL BIRK AS?

Axel Birk is registered as general manager of AXEL BIRK AS.

Where is AXEL BIRK AS based?

AXEL BIRK AS has its business address in Skreia.

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.