BIZTRAC BETA
Buying and selling of own real estate

ITAMAR AS

Org. no. 918326529 Limited company (AS) Haugesund Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −38,000
Equity NOK 44.7m
Incorporated 2016
Share capital NOK 1.7m

Signals

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

ITAMAR AS is registered as a limited company in Haugesund, Rogaland with organisation number 918326529. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2016. Registered share capital is NOK 1.7m, divided into 50 shares. The company's stated purpose is: “Investering og forvaltning av egne driftsmidler i fast eiendom, aksjer og andre finansinvesteringer, herunder å delta i andre selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −38,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −38,000
Equity
NOK 44.7m
Est. value
NOK 40.8m

Financial health · 2024

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

Who owns ITAMAR AS?

JAN IDAR VIKSE
ITAMAR AS
NOK 0 rev. · NOK −38,000 profit

ITAMAR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ITAMAR AS own?

ITAMAR AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ITAMAR AS

Who owns ITAMAR AS?

JAN IDAR VIKSE is the largest registered owner, with 100.0%.

What is the revenue of ITAMAR AS?

ITAMAR AS had revenue of NOK 0 in 2024.

Who is the general manager of ITAMAR AS?

Jan Idar Vikse is registered as general manager of ITAMAR AS.

Where is ITAMAR AS based?

ITAMAR AS has its business address in Haugesund.

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.