BIZTRAC BETA
Rental and operating of own or leased real estate

VARNAVEIEN 22 AS

Org. no. 812749242 Limited company (AS) Oslo Incorporated 1980 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 2.4m
Equity NOK 4.4m
Incorporated 1980
Share capital NOK 920,000

Signals

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

VARNAVEIEN 22 AS is registered as a limited company in Oslo, Oslo with organisation number 812749242. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1980. Registered share capital is NOK 920,000, divided into 100000 shares. The company's stated purpose is: “Investering i fast eiendom og verdipapirer, samt næringsvirksomhet av enhver art, herunder deltagelse i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 2.4m
Equity
NOK 4.4m
Est. value
NOK 7.0m

Financial health · 2025

Liquidity
0.37
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.5%
Satisfactory
Equity as a share of total capital

Who owns VARNAVEIEN 22 AS?

RABEKKGATA HOLDING AS
VARNAVEIEN 22 AS
NOK 4.6m rev. · NOK 2.4m profit

VARNAVEIEN 22 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

VARNAVEIEN 22 AS er morselskap for 2 datterselskaper:

Frequently asked questions about VARNAVEIEN 22 AS

Who owns VARNAVEIEN 22 AS?

RABEKKGATA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VARNAVEIEN 22 AS?

VARNAVEIEN 22 AS had revenue of NOK 4.6m in 2025.

Where is VARNAVEIEN 22 AS based?

VARNAVEIEN 22 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.