BIZTRAC BETA
Other real estate activities on a fee or contract basis

BEITOSTØLEN AS

Org. no. 990590222 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 5,000
Equity NOK 55.8m
Incorporated 2006
Share capital NOK 1.1m

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-05-31 Adresseendring registrert 2026-05-31.

BEITOSTØLEN AS is registered as a limited company in Oslo, Oslo with organisation number 990590222. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2006. Registered share capital is NOK 1.1m, divided into 1100 shares. The company's stated purpose is: “Eie, kjøpe, selge og leie ut fast eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 5,000
Equity
NOK 55.8m
Est. value
NOK 40.2m

Financial health · 2025

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

Who owns BEITOSTØLEN AS?

COOP NORGE EIENDOM AS
BEITOSTØLEN AS
NOK 3.3m rev. · NOK 5,000 profit

BEITOSTØLEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BEITOSTØLEN AS

Who owns BEITOSTØLEN AS?

COOP NORGE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BEITOSTØLEN AS?

BEITOSTØLEN AS had revenue of NOK 3.3m in 2025.

Where is BEITOSTØLEN AS based?

BEITOSTØLEN 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.