BIZTRAC BETA
Development of building projects

NILSENUTEN AS

Org. no. 984012217 Limited company (AS) Hol Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK −361,000
Incorporated 2001
Share capital NOK 352,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−361k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

NILSENUTEN AS is registered as a limited company in Hol, Buskerud with organisation number 984012217. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2001. Registered share capital is NOK 352,000, divided into 1760 shares. The company's stated purpose is: “Utvikling, bygging, kjøp, salg og utleie av eiendom og annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK −361,000

Financial health · 2024

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

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

Who owns NILSENUTEN AS?

JARLE PÅLGARDHAUGEN
NILSENUTEN AS
NOK 0 rev. · NOK −7,000 profit

NILSENUTEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NILSENUTEN AS

Who owns NILSENUTEN AS?

JARLE PÅLGARDHAUGEN is the largest registered owner, with 68.2%.

What is the revenue of NILSENUTEN AS?

NILSENUTEN AS had revenue of NOK 0 in 2024.

Who is the general manager of NILSENUTEN AS?

Kristin Pålgardhaugen is registered as general manager of NILSENUTEN AS.

Where is NILSENUTEN AS based?

NILSENUTEN AS has its business address in Geilo.

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.