BIZTRAC BETA
Development of building projects

KREATIV UTVIKLING AS

Org. no. 916100086 Limited company (AS) Lillestrøm Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1,000
Equity NOK 4.8m
Incorporated 2015
Share capital NOK 30,000

Signals

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

KREATIV UTVIKLING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 916100086. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Eiendomsutvikling og oppføring av nybygg, investeringer i aksjer og selskapsandeler og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 4.8m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns KREATIV UTVIKLING AS?

HB HANSEN HOLDING AS
KREATIV UTVIKLING AS
NOK 0 rev. · NOK −1,000 profit

KREATIV UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KREATIV UTVIKLING AS

Who owns KREATIV UTVIKLING AS?

HB HANSEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of KREATIV UTVIKLING AS?

KREATIV UTVIKLING AS had revenue of NOK 0 in 2024.

Who is the general manager of KREATIV UTVIKLING AS?

Jørn Elvegård is registered as general manager of KREATIV UTVIKLING AS.

Where is KREATIV UTVIKLING AS based?

KREATIV UTVIKLING AS has its business address in Skedsmokorset.

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.