BIZTRAC BETA
Wholesale of motor vehicles

VOGN-SERVICE AS

Org. no. 821523842 Limited company (AS) Fredrikstad Incorporated 1971 Active
Ownership graph ↗
Revenue 2025 NOK 22.2m
Operating profit NOK −74,000
Equity NOK 11.8m
Incorporated 1971
Employees 10
Share capital NOK 80,000

Signals

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

VOGN-SERVICE AS is registered as a limited company in Fredrikstad, Østfold with organisation number 821523842. The business is classified under wholesale of motor vehicles (NACE 46.710). The company was incorporated in 1971 and has 10 registered employees. Registered share capital is NOK 80,000, divided into 40 shares. The company's stated purpose is: “Reparasjoner og vedlikehold av lastebiltilhengere, semitrailere, kraner etc., samt omsetning og servicetjenester av samme.”. The most recent filed accounts, for the 2025 financial year, show NOK 22.2m in revenue and NOK −74,000 in operating profit.

Key figures · 2025

Revenue
NOK 22.2m
Operating profit
NOK −74,000
Equity
NOK 11.8m
Est. value
NOK 11.7m

Financial health · 2025

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

Who owns VOGN-SERVICE AS?

HEIMO HOLDING AS
VOGN-SERVICE AS
NOK 22.2m rev. · NOK −74,000 profit

VOGN-SERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VOGN-SERVICE AS

Who owns VOGN-SERVICE AS?

HEIMO HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of VOGN-SERVICE AS?

VOGN-SERVICE AS had revenue of NOK 22.2m in 2025.

Who is the general manager of VOGN-SERVICE AS?

Tommy Andre Eriksen is registered as general manager of VOGN-SERVICE AS.

Where is VOGN-SERVICE AS based?

VOGN-SERVICE AS has its business address in Torp.

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.