BIZTRAC BETA
Development of building projects

NODELAND UTVIKLING AS

Org. no. 988020273 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −113,000
Equity NOK −1.6m
Incorporated 2005
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−113k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NODELAND UTVIKLING AS is registered as a limited company in Kristiansand, Agder with organisation number 988020273. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie, utleie og utvikling av fast eiendom med alt som hermed står i forbindelse, samt deltakelse i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −113,000
Equity
NOK −1.6m

Financial health · 2024

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

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

Who owns NODELAND UTVIKLING AS?

THORSLAND INVEST AS
NODELAND UTVIKLING AS
· NOK −113,000 profit

NODELAND UTVIKLING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about NODELAND UTVIKLING AS

Who owns NODELAND UTVIKLING AS?

THORSLAND INVEST AS is the largest registered owner, with 60.0%.

Who is the general manager of NODELAND UTVIKLING AS?

Roy Gundersen is registered as general manager of NODELAND UTVIKLING AS.

Where is NODELAND UTVIKLING AS based?

NODELAND UTVIKLING AS has its business address in Kristiansand S.

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.