BIZTRAC BETA
Rental and operating of own or leased real estate

VINJE VIKEN AS

Org. no. 926438948 Limited company (AS) Ås Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −45,000
Equity NOK 48,000
Incorporated 2021
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−45k kr).

VINJE VIKEN AS is registered as a limited company in Ås, Akershus with organisation number 926438948. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 200 shares. The company's stated purpose is: “Utleie av fast eiendom og vaktmestertjenester, og alt det som hører naturlig inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −45,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −45,000
Equity
NOK 48,000
Est. value
NOK 2.2m

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VINJE VIKEN AS?

JØRN OLAV VINJE TOMTER
VINJE VIKEN AS
NOK 1.4m rev. · NOK −45,000 profit

VINJE VIKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VINJE VIKEN AS

Who owns VINJE VIKEN AS?

JØRN OLAV VINJE TOMTER is the largest registered owner, with 100.0%.

What is the revenue of VINJE VIKEN AS?

VINJE VIKEN AS had revenue of NOK 1.4m in 2024.

Who is the general manager of VINJE VIKEN AS?

Jørn Olav Vinje Tomter is registered as general manager of VINJE VIKEN AS.

Where is VINJE VIKEN AS based?

VINJE VIKEN AS has its business address in Ås.

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.