BIZTRAC BETA
Rental and operating of own or leased real estate

RINGERIKSVEIEN 70 AS

Org. no. 990400636 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 8.2m
Operating profit NOK 6.7m
Equity NOK 105.4m
Incorporated 2006
Share capital NOK 400,000

Signals

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

RINGERIKSVEIEN 70 AS is registered as a limited company in Oslo, Oslo with organisation number 990400636. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 400,000, divided into 200 shares. The company's stated purpose is: “Erverv, utvikling og utleie av fast eiendom samt det som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.2m in revenue and NOK 6.7m in operating profit.

Key figures · 2024

Revenue
NOK 8.2m
Operating profit
NOK 6.7m
Equity
NOK 105.4m
Est. value
NOK 89.1m

Financial health · 2024

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

Who owns RINGERIKSVEIEN 70 AS?

FABRITIUS GRUPPEN AS
RINGERIKSVEIEN 70 AS
NOK 8.2m rev. · NOK 6.7m profit

RINGERIKSVEIEN 70 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RINGERIKSVEIEN 70 AS er morselskap for 33 datterselskaper:

Frequently asked questions about RINGERIKSVEIEN 70 AS

Who owns RINGERIKSVEIEN 70 AS?

FABRITIUS GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of RINGERIKSVEIEN 70 AS?

RINGERIKSVEIEN 70 AS had revenue of NOK 8.2m in 2024.

Where is RINGERIKSVEIEN 70 AS based?

RINGERIKSVEIEN 70 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.