BIZTRAC BETA
Sports activities n.e.c.

BIRKEN AS

Org. no. 912889912 Limited company (AS) Åmot Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 36.8m
Operating profit NOK 1.0m
Equity NOK 5.8m
Incorporated 2013
Employees 38
Share capital NOK 1.0m

Signals

1 flags
  • Nylig endring 2026-04-09 Adresseendring registrert 2026-04-09.

BIRKEN AS is registered as a limited company in Åmot, Innlandet with organisation number 912889912. The business is classified under sports activities n.e.c. (NACE 93.190). The company was incorporated in 2013 and has 38 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Drive ideell virksomhet ved å fremme interesse for ski, sykling, løp og annen breddeidrett ved å arrangere Birkebeinerrittet, Birkebeinerrennet og Birkebeinerløpet og lignede breddeidrettsarrangement herunder som eier av selskaper som driver lignende virksomhet for å fremme interessen for ski, sykling, løp og annen breddeidrett.”. The most recent filed accounts, for the 2024 financial year, show NOK 36.8m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 36.8m
Operating profit
NOK 1.0m
Equity
NOK 5.8m
Est. value
NOK 7.0m

Financial health · 2024

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.9%
Good
Equity as a share of total capital

Who owns BIRKEN AS?

No shareholders are registered for BIRKEN AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BIRKEN AS

What is the revenue of BIRKEN AS?

BIRKEN AS had revenue of NOK 36.8m in 2024.

Who is the general manager of BIRKEN AS?

Jostein Buraas is registered as general manager of BIRKEN AS.

Where is BIRKEN AS based?

BIRKEN AS has its business address in Rena.

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.