BIZTRAC BETA
Civil engineering activities

IKON NORGE PROSJEKT AS

Org. no. 934951352 Limited company (AS) Lillestrøm Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2024
Employees 13
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-21 Adresseendring registrert 2026-04-21.

IKON NORGE PROSJEKT AS is registered as a limited company in Lillestrøm, Akershus with organisation number 934951352. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2024 and has 13 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utføre anlegg- og byggoppdrag som entreprenør samt virksomhet som er i naturlig sammenheng med denne bransje og nærstående bransjer. Selskapets formål omfatter også produksjon, import, montasje av utstyr, materialer, verktøy og maskiner til anlegg, mekanisk industri og fornybar energi.”.

Key figures · 2024

Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 49,000

Financial health · 2024

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

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

Who owns IKON NORGE PROSJEKT AS?

BERG INNOVASJON AS
IKON NORGE PROSJEKT AS
· NOK 0 profit

IKON NORGE PROSJEKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IKON NORGE PROSJEKT AS

Who owns IKON NORGE PROSJEKT AS?

BERG INNOVASJON AS is the largest registered owner, with 100.0%.

Who is the general manager of IKON NORGE PROSJEKT AS?

Jørgen Sikkeland is registered as general manager of IKON NORGE PROSJEKT AS.

Where is IKON NORGE PROSJEKT AS based?

IKON NORGE PROSJEKT AS has its business address in Lillestrøm.

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.