BIZTRAC BETA
Other specialised construction activities n.e.c.

JP BYGG OG BETONG AS

Org. no. 923846700 Limited company (AS) Gjøvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK −12,000
Equity NOK 453,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

JP BYGG OG BETONG AS is registered as a limited company in Gjøvik, Innlandet with organisation number 923846700. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 75 shares. The company's stated purpose is: “Ulike oppgaver innenfor bygg og anleggsbransjen, da i all hovedsak betongarbeid og rivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK −12,000
Equity
NOK 453,000
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns JP BYGG OG BETONG AS?

PER EINAR PETTERSEN
JP BYGG OG BETONG AS
NOK 4.2m rev. · NOK −12,000 profit

JP BYGG OG BETONG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about JP BYGG OG BETONG AS

Who owns JP BYGG OG BETONG AS?

PER EINAR PETTERSEN is the largest registered owner, with 40.0%.

What is the revenue of JP BYGG OG BETONG AS?

JP BYGG OG BETONG AS had revenue of NOK 4.2m in 2024.

Who is the general manager of JP BYGG OG BETONG AS?

Per Einar Pettersen is registered as general manager of JP BYGG OG BETONG AS.

Where is JP BYGG OG BETONG AS based?

JP BYGG OG BETONG AS has its business address in Hunndalen.

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.