BIZTRAC BETA
COMPANY REGISTER PROFILE
825867252 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

VINJA AS

Org. no. 825867252 Limited company (AS) Tønsberg Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK 9.4m
Incorporated 2020
Share capital NOK 168,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).

VINJA AS is registered as a limited company in Tønsberg, Vestfold with organisation number 825867252. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 168,000, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder å eie andeler i andre selskap.”.

Key figures · 2025

Operating profit
NOK −17,000
Equity
NOK 9.4m
Est. value
NOK 8.8m

Financial health · 2025

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

Who owns VINJA AS?

VINJA AS has 4 registered shareholders:

All shareholders and roles →

Which companies does VINJA AS own?

VINJA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VINJA AS

Who owns VINJA AS?

CECILIE ØDEGÅRD SVIHUS is the largest registered owner, with 30.0%.

Where is VINJA AS based?

VINJA AS has its business address in Tønsberg.

Property

Business address c/o Turid Aas Ødegård Døsserødveien 13B, 3118 Tønsberg
Cadastral unit 3905-148/316/0/0
Building Store sammenbygde boligbygg på 3 og 4 etg · 16 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.