BIZTRAC BETA
COMPANY REGISTER PROFILE
989219510 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 02.09.2026
UVDAL SNEKKERSERVICE AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Uoppgitt

UVDAL SNEKKERSERVICE AS

Org. no. 989219510 Limited company (AS) Nore Og Uvdal Incorporated 2005 In liquidation
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK −143,000
Incorporated 2005
Share capital NOK 419,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−143k kr).
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

UVDAL SNEKKERSERVICE AS is registered as a limited company in Nore Og Uvdal, Buskerud with organisation number 989219510. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 419,000, divided into 34 shares. The company's stated purpose is: “Investering i aksjer og fast eiendom, oppføring, vedlikehold og omsetning av bygninger, samt det som faller naturlig inn under dette.”.

Former names: NØRSTEBØ INVEST AS

Key figures · 2025

Operating profit
NOK −12,000
Equity
NOK −143,000

Financial health · 2025

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

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

Who owns UVDAL SNEKKERSERVICE AS?

UVDAL SNEKKERSERVICE AS
· NOK −12,000 profit

UVDAL SNEKKERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UVDAL SNEKKERSERVICE AS

Who owns UVDAL SNEKKERSERVICE AS?

GEIR NØRSTEBØ is the largest registered owner, with 100.0%.

Where is UVDAL SNEKKERSERVICE AS based?

UVDAL SNEKKERSERVICE AS has its business address in Uvdal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.