BIZTRAC BETA
Rental and operating of own or leased real estate

VÅRVEIEN 21 AS

Org. no. 984773870 Limited company (AS) Drammen Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 995,000
Operating profit NOK 704,000
Equity NOK 7.3m
Incorporated 2002
Share capital NOK 160,000

Signals

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

VÅRVEIEN 21 AS is registered as a limited company in Drammen, Buskerud with organisation number 984773870. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 160,000, divided into 10000 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 995,000 in revenue and NOK 704,000 in operating profit.

Key figures · 2025

Revenue
NOK 995,000
Operating profit
NOK 704,000
Equity
NOK 7.3m
Est. value
NOK 6.9m

Financial health · 2025

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

Who owns VÅRVEIEN 21 AS?

KILAR AS
VÅRVEIEN 21 AS
NOK 995,000 rev. · NOK 704,000 profit

VÅRVEIEN 21 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VÅRVEIEN 21 AS

Who owns VÅRVEIEN 21 AS?

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

What is the revenue of VÅRVEIEN 21 AS?

VÅRVEIEN 21 AS had revenue of NOK 995,000 in 2025.

Who is the general manager of VÅRVEIEN 21 AS?

Bjørnar Kildebo is registered as general manager of VÅRVEIEN 21 AS.

Where is VÅRVEIEN 21 AS based?

VÅRVEIEN 21 AS has its business address in Drammen.

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.