BIZTRAC BETA
Retail sale of motor vehicles

VIKEBY HOLDING AS

Org. no. 825114572 Limited company (AS) Marker Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −24,000
Equity NOK 6.2m
Incorporated 2020
Share capital NOK 290,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−24k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VIKEBY HOLDING AS is registered as a limited company in Marker, Østfold with organisation number 825114572. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2020. Registered share capital is NOK 290,000, divided into 100 shares. The company's stated purpose is: “Investeringer og alt som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 6.2m
Est. value
NOK 30.1m

Financial health · 2025

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

Who owns VIKEBY HOLDING AS?

ODD EINAR VIKEBY
VIKEBY HOLDING AS
NOK 0 rev. · NOK −24,000 profit

VIKEBY HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VIKEBY HOLDING AS own?

VIKEBY HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VIKEBY HOLDING AS

Who owns VIKEBY HOLDING AS?

ODD EINAR VIKEBY is the largest registered owner, with 50.0%.

What is the revenue of VIKEBY HOLDING AS?

VIKEBY HOLDING AS had revenue of NOK 0 in 2025.

Where is VIKEBY HOLDING AS based?

VIKEBY HOLDING AS has its business address in Ørje.

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.