BIZTRAC BETA
Computer programming activities

JOMON AS

Org. no. 913068025 Limited company (AS) Stavanger Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 58,000
Operating profit NOK −159,000
Equity NOK 4.2m
Incorporated 2014
Share capital NOK 30,000

Signals

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

JOMON AS is registered as a limited company in Stavanger, Rogaland with organisation number 913068025. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Support, drift og utvikling av dataløsninger, kjøp, salg og drift av fast eiendom samt kjøp av aksjer eller på annen måte delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 58,000 in revenue and NOK −159,000 in operating profit.

Key figures · 2024

Revenue
NOK 58,000
Operating profit
NOK −159,000
Equity
NOK 4.2m
Est. value
NOK 7.5m

Financial health · 2024

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

Who owns JOMON AS?

SINDRE HAALAND
JOMON AS
NOK 58,000 rev. · NOK −159,000 profit

JOMON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JOMON AS own?

JOMON AS holds stakes in 14 companies:

See the full ownership structure →

Frequently asked questions about JOMON AS

Who owns JOMON AS?

SINDRE HAALAND is the largest registered owner, with 100.0%.

What is the revenue of JOMON AS?

JOMON AS had revenue of NOK 58,000 in 2024.

Who is the general manager of JOMON AS?

Sindre Haaland is registered as general manager of JOMON AS.

Where is JOMON AS based?

JOMON AS has its business address in Stavanger.

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.