biztrac. BETA
COMPANY REGISTER PROFILE
926373641 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

GJØVIK MASKINDRIFT AS

Org. no. 926373641 Limited company (AS) Gjøvik Incorporated 2020 Active
Revenue 2025 NOK 8.8m
Operating profit NOK 71,000
Equity NOK 1.3m
Incorporated 2020
Employees 6
Share capital NOK 50,000

GJØVIK MASKINDRIFT AS is registered as a limited company in Gjøvik, Innlandet with organisation number 926373641. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2020 and has 6 registered employees. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Alt av graving og det som naturlig forbindes med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.8m in revenue and NOK 71,000 in operating profit.

Former names: HEMLI BOLIG-UTVIKLING AS

Key figures · 2025

Revenue
NOK 8.8m
▼ −17 %
Operating profit
NOK 71,000
▼ −88 %
Equity
NOK 1.3m
▼ −3 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.60
Good
Current assets ÷ current liabilities
Profitability
2.0%
Weak
Return on total assets
Solidity
39.0%
Good
Equity as a share of total capital

Who owns GJØVIK MASKINDRIFT AS?

GJØVIK MASKINDRIFT AS
NOK 8.8m rev. · NOK 71,000 profit

GJØVIK MASKINDRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GJØVIK MASKINDRIFT AS

Who owns GJØVIK MASKINDRIFT AS?

Bjørn Henning Christensen is the largest registered owner, with 64.6%.

What is the revenue of GJØVIK MASKINDRIFT AS?

GJØVIK MASKINDRIFT AS had revenue of NOK 8.8m in 2025.

Who is the general manager of GJØVIK MASKINDRIFT AS?

Bjørn Henning Christensen is registered as general manager of GJØVIK MASKINDRIFT AS.

Where is GJØVIK MASKINDRIFT AS based?

GJØVIK MASKINDRIFT AS has its business address in Hunndalen.

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.