BIZTRAC BETA
COMPANY REGISTER PROFILE
997633555 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

BJORBEKK TERRASSE AS

Org. no. 997633555 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 5.4m
Operating profit NOK 3.3m
Equity NOK 6.3m
Incorporated 2011
Share capital NOK 2.9m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BJORBEKK TERRASSE AS is registered as a limited company in Oslo, Oslo with organisation number 997633555. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 2.9m, divided into 2900 shares. The company's stated purpose is: “Investeringsvirksomhet og utvikling tilknyttet fast eiendom og dertil hørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.4m in revenue and NOK 3.3m in operating profit.

Key figures · 2025

Revenue
NOK 5.4m
▲ +10 %
Operating profit
NOK 3.3m
▲ +18 %
Equity
NOK 6.3m
▼ −3 %
Est. value
NOK 9.7m

Financial health · 2025

Liquidity
2.87
Very good
Current assets ÷ current liabilities
Profitability
10.7%
Good
Return on total assets
Solidity
17.1%
Satisfactory
Equity as a share of total capital

Who owns BJORBEKK TERRASSE AS?

BJORBEKK TERRASSE AS
NOK 5.4m rev. · NOK 3.3m profit

BJORBEKK TERRASSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJORBEKK TERRASSE AS

Who owns BJORBEKK TERRASSE AS?

SCANDIA AS is the largest registered owner, with 100.0%.

What is the revenue of BJORBEKK TERRASSE AS?

BJORBEKK TERRASSE AS had revenue of NOK 5.4m in 2025.

Where is BJORBEKK TERRASSE AS based?

BJORBEKK TERRASSE 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 02.09.2026.

Report a problem

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