biztrac. BETA
COMPANY REGISTER PROFILE
824463182 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

JERNVERKSTOMTA UTBYGGING AS

Org. no. 824463182 Limited company (AS) Porsgrunn Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −153,000
Equity NOK −72,000
Incorporated 2019
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−72k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−153k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JERNVERKSTOMTA UTBYGGING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 824463182. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom, samt ellers hva som er naturlig i tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −153,000
▼ −124 %
Equity
NOK −72,000
▼ −204 %
Est. value
NOK 16.3m

Financial health · 2025

Liquidity
0.94
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-0.5%
Weak
Equity as a share of total capital

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

Who owns JERNVERKSTOMTA UTBYGGING AS?

JERNVERKSTOMTA UTBYGGING AS
· NOK −153,000 profit

JERNVERKSTOMTA UTBYGGING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about JERNVERKSTOMTA UTBYGGING AS

Who owns JERNVERKSTOMTA UTBYGGING AS?

GBBL PROSJEKT AS is the largest registered owner, with 51.0%.

Where is JERNVERKSTOMTA UTBYGGING AS based?

JERNVERKSTOMTA UTBYGGING AS has its business address in Porsgrunn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.