BIZTRAC BETA
Site preparation

GJERSVIK MASKINDRIFT AS

Org. no. 929229010 Limited company (AS) Fauske Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 106,000
Equity NOK 37,000
Incorporated 2022
Share capital NOK 50,000

GJERSVIK MASKINDRIFT AS is registered as a limited company in Fauske, Nordland with organisation number 929229010. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Anlegg, veivedlikehold, kjøp og salg, samt andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 106,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 106,000
Equity
NOK 37,000
Est. value
NOK 322,000

Financial health · 2024

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.5%
Weak
Equity as a share of total capital

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

Who owns GJERSVIK MASKINDRIFT AS?

CHRISTIAN RUTHBERG GJERSVIK
GJERSVIK MASKINDRIFT AS
NOK 1.2m rev. · NOK 106,000 profit

GJERSVIK MASKINDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJERSVIK MASKINDRIFT AS

Who owns GJERSVIK MASKINDRIFT AS?

CHRISTIAN RUTHBERG GJERSVIK is the largest registered owner, with 100.0%.

What is the revenue of GJERSVIK MASKINDRIFT AS?

GJERSVIK MASKINDRIFT AS had revenue of NOK 1.2m in 2024.

Where is GJERSVIK MASKINDRIFT AS based?

GJERSVIK MASKINDRIFT AS has its business address in Fauske.

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.