biztrac. BETA
COMPANY REGISTER PROFILE
924765410 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

GJØVIKTERMINALEN AS

Org. no. 924765410 Limited company (AS) Gjøvik Incorporated 2020 Active
Revenue 2025 NOK 7.4m
Operating profit NOK −183,000
Equity NOK −230,000
Incorporated 2020
Share capital NOK 1.2m

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−230k kr).

GJØVIKTERMINALEN AS is registered as a limited company in Gjøvik, Innlandet with organisation number 924765410. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2020. Registered share capital is NOK 1.2m, divided into 1200 shares. The company's stated purpose is: “Transport og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.4m in revenue and NOK −183,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.4m
▼ −10 %
Operating profit
NOK −183,000
▼ −327 %
Equity
NOK −230,000
▼ −291 %

Financial health · 2025

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
-5.5%
Not satisfactory
Return on total assets
Solidity
-8.3%
Weak
Equity as a share of total capital

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

Who owns GJØVIKTERMINALEN AS?

GJØVIKTERMINALEN AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about GJØVIKTERMINALEN AS

Who owns GJØVIKTERMINALEN AS?

SVEUM EIENDOM AS is the largest registered owner, with 37.5%.

What is the revenue of GJØVIKTERMINALEN AS?

GJØVIKTERMINALEN AS had revenue of NOK 7.4m in 2025.

Who is the general manager of GJØVIKTERMINALEN AS?

Håkon Sveum is registered as general manager of GJØVIKTERMINALEN AS.

Where is GJØVIKTERMINALEN AS based?

GJØVIKTERMINALEN AS has its business address in Gjøvik.

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

Report a problem

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