BIZTRAC BETA
Site preparation

KLINGEN MASKINENTREPRENØR AS

Org. no. 912027228 Limited company (AS) Namsos Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 13.7m
Operating profit NOK 1.3m
Equity NOK 4.3m
Incorporated 2013
Employees 9
Share capital NOK 30,000

KLINGEN MASKINENTREPRENØR AS is registered as a limited company in Namsos, Trøndelag with organisation number 912027228. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2013 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Maskinentreprenørvirksomhet, utvinning av grus og fjell samt annet som naturlig hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.7m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 13.7m
Operating profit
NOK 1.3m
Equity
NOK 4.3m
Est. value
NOK 6.3m

Financial health · 2024

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

Who owns KLINGEN MASKINENTREPRENØR AS?

KLINGEN EIENDOM AS
KLINGEN MASKINENTREPRENØR AS
NOK 13.7m rev. · NOK 1.3m profit

KLINGEN MASKINENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLINGEN MASKINENTREPRENØR AS

Who owns KLINGEN MASKINENTREPRENØR AS?

KLINGEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KLINGEN MASKINENTREPRENØR AS?

KLINGEN MASKINENTREPRENØR AS had revenue of NOK 13.7m in 2024.

Who is the general manager of KLINGEN MASKINENTREPRENØR AS?

Geir Arne Klingen is registered as general manager of KLINGEN MASKINENTREPRENØR AS.

Where is KLINGEN MASKINENTREPRENØR AS based?

KLINGEN MASKINENTREPRENØR AS has its business address in Spillum.

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.