BIZTRAC BETA
Construction of residential and non-residential buildings

GM ENTREPRENØR AS

Org. no. 890016162 Limited company (AS) Kongsberg Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 16,000
Incorporated 2006
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11k kr).

GM ENTREPRENØR AS is registered as a limited company in Kongsberg, Buskerud with organisation number 890016162. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet ved betongarbeid, muring og flislegging samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper ved aksjetegning eller på annen måte.”.

Key figures · 2024

Operating profit
NOK −11,000
Equity
NOK 16,000
Est. value
NOK 77,000

Financial health · 2024

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

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

Who owns GM ENTREPRENØR AS?

GEIR FRODE MARTINSEN
GM ENTREPRENØR AS
· NOK −11,000 profit

GM ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GM ENTREPRENØR AS own?

GM ENTREPRENØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GM ENTREPRENØR AS

Who owns GM ENTREPRENØR AS?

GEIR FRODE MARTINSEN is the largest registered owner, with 100.0%.

Who is the general manager of GM ENTREPRENØR AS?

Geir Frode Martinsen is registered as general manager of GM ENTREPRENØR AS.

Where is GM ENTREPRENØR AS based?

GM ENTREPRENØR AS has its business address in Kongsberg.

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.