BIZTRAC BETA
Rental and operating of own or leased real estate

VÅRVEIEN 20 AS

Org. no. 829649292 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 310,000
Equity NOK 1.4m
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-09 Adresseendring registrert 2026-06-09.

VÅRVEIEN 20 AS is registered as a limited company in Drammen, Buskerud with organisation number 829649292. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 50 shares. The company's stated purpose is: “Å eie og forvalte fast eiendom og virksomhet som står i forbindelse med dette, herunder å eie andeler og aksjer i andre selskaper med likeartet formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 310,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 310,000
Equity
NOK 1.4m
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.3%
Satisfactory
Equity as a share of total capital

Who owns VÅRVEIEN 20 AS?

TEKO INVEST AS
VÅRVEIEN 20 AS
NOK 1.4m rev. · NOK 310,000 profit

VÅRVEIEN 20 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VÅRVEIEN 20 AS

Who owns VÅRVEIEN 20 AS?

TEKO INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of VÅRVEIEN 20 AS?

VÅRVEIEN 20 AS had revenue of NOK 1.4m in 2025.

Where is VÅRVEIEN 20 AS based?

VÅRVEIEN 20 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.