BIZTRAC BETA
Repair and maintenance of motor vehicles

KOKSLIEN MASKINSERVICE AS

Org. no. 929507584 Limited company (AS) Gjøvik Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK 402,000
Equity NOK 1.2m
Incorporated 2022
Share capital NOK 100,000

KOKSLIEN MASKINSERVICE AS is registered as a limited company in Gjøvik, Innlandet with organisation number 929507584. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Vedlikehold og reparasjon av maskiner og motorvogner, samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK 402,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK 402,000
Equity
NOK 1.2m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns KOKSLIEN MASKINSERVICE AS?

HANS EINAR KOKSLIEN
KOKSLIEN MASKINSERVICE AS
NOK 4.7m rev. · NOK 402,000 profit

KOKSLIEN MASKINSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOKSLIEN MASKINSERVICE AS

Who owns KOKSLIEN MASKINSERVICE AS?

HANS EINAR KOKSLIEN is the largest registered owner, with 100.0%.

What is the revenue of KOKSLIEN MASKINSERVICE AS?

KOKSLIEN MASKINSERVICE AS had revenue of NOK 4.7m in 2024.

Who is the general manager of KOKSLIEN MASKINSERVICE AS?

Hans Einar Kokslien is registered as general manager of KOKSLIEN MASKINSERVICE AS.

Where is KOKSLIEN MASKINSERVICE AS based?

KOKSLIEN MASKINSERVICE AS has its business address in Snertingdal.

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.