biztrac. BETA
COMPANY REGISTER PROFILE
917708363 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BJØRNSONS HAGE 3 AS

Org. no. 917708363 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 491,000
Operating profit NOK 51,000
Equity NOK 894,000
Incorporated 2016
Share capital NOK 120,000

BJØRNSONS HAGE 3 AS is registered as a limited company in Oslo, Oslo with organisation number 917708363. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 120,000, divided into 12000 shares. The company's stated purpose is: “Kjøp, bygging og salg av eiendommer i Skedsmo kommune.”. The most recent filed accounts, for the 2025 financial year, show NOK 491,000 in revenue and NOK 51,000 in operating profit.

Key figures · 2025

Revenue
NOK 491,000
▲ +16 %
Operating profit
NOK 51,000
▼ −69 %
Equity
NOK 894,000
▲ +9 %
Est. value
NOK 817,000

Financial health · 2025

Liquidity
-448.97
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
2.1%
Not satisfactory
Equity as a share of total capital

Who owns BJØRNSONS HAGE 3 AS?

BJØRNSONS HAGE 3 AS
NOK 491,000 rev. · NOK 51,000 profit

BJØRNSONS HAGE 3 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BJØRNSONS HAGE 3 AS

Who owns BJØRNSONS HAGE 3 AS?

AF GRUPPEN NORGE AS is the largest registered owner, with 50.0%.

What is the revenue of BJØRNSONS HAGE 3 AS?

BJØRNSONS HAGE 3 AS had revenue of NOK 491,000 in 2025.

Who is the general manager of BJØRNSONS HAGE 3 AS?

Tormod Søbyskogen is registered as general manager of BJØRNSONS HAGE 3 AS.

Where is BJØRNSONS HAGE 3 AS based?

BJØRNSONS HAGE 3 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.