BIZTRAC BETA
Civil engineering activities

GP BYGGKONTROLL AS

Org. no. 932832712 Limited company (AS) Gjøvik Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 68,000
Operating profit NOK −10,000
Equity NOK −130
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−130 kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

GP BYGGKONTROLL AS is registered as a limited company in Gjøvik, Innlandet with organisation number 932832712. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Byggeteknisk konsulentvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 68,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 68,000
Operating profit
NOK −10,000
Equity
NOK −130

Financial health · 2024

Liquidity
1.64
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.7%
Weak
Equity as a share of total capital

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

Who owns GP BYGGKONTROLL AS?

GØRIL MICHALSEN
GP BYGGKONTROLL AS
NOK 68,000 rev. · NOK −10,000 profit

GP BYGGKONTROLL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GP BYGGKONTROLL AS

Who owns GP BYGGKONTROLL AS?

GØRIL MICHALSEN is the largest registered owner, with 50.0%.

What is the revenue of GP BYGGKONTROLL AS?

GP BYGGKONTROLL AS had revenue of NOK 68,000 in 2024.

Who is the general manager of GP BYGGKONTROLL AS?

Petter Erlandsen is registered as general manager of GP BYGGKONTROLL AS.

Where is GP BYGGKONTROLL AS based?

GP BYGGKONTROLL AS has its business address in Gjøvik.

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.