BIZTRAC BETA
Construction of residential and non-residential buildings

JOME INVEST AS

Org. no. 916986238 Limited company (AS) Bamble Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −38,000
Equity NOK 348,000
Incorporated 2016
Share capital NOK 36,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−38k kr).

JOME INVEST AS is registered as a limited company in Bamble, Telemark with organisation number 916986238. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 36,000, divided into 36 shares. The company's stated purpose is: “Investering i aksjer. Kjøp, salg, utleie og utvikling av eiendom. Kjøp og salg av varer og tjenester for øvrig og det som naturlig hører herunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −38,000
Equity
NOK 348,000
Est. value
NOK 366,000

Financial health · 2025

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

Who owns JOME INVEST AS?

GUNNAR KRISTENSEN
JOME INVEST AS
NOK 0 rev. · NOK −38,000 profit

JOME INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JOME INVEST AS own?

JOME INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JOME INVEST AS

Who owns JOME INVEST AS?

GUNNAR KRISTENSEN is the largest registered owner, with 50.0%.

What is the revenue of JOME INVEST AS?

JOME INVEST AS had revenue of NOK 0 in 2025.

Where is JOME INVEST AS based?

JOME INVEST AS has its business address in Stathelle.

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.