biztrac. BETA
COMPANY REGISTER PROFILE
931922106 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

ØVRE NESBYGDA AS

Org. no. 931922106 Limited company (AS) Drammen Incorporated 2023 Active
Revenue 2025 NOK 0
Operating profit NOK −33,000
Equity NOK −2.6m
Incorporated 2023
Share capital NOK 60,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,6 mill kr).

ØVRE NESBYGDA AS is registered as a limited company in Drammen, Buskerud with organisation number 931922106. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og forvaltning av fast eiendom og alt som står i naturlig forbindelse med dette, herunder investeringer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −33,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −33,000
▼ −19 %
Equity
NOK −2.6m
▼ −205 %

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
-13.8%
Weak
Equity as a share of total capital

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

Who owns ØVRE NESBYGDA AS?

ØVRE NESBYGDA AS
NOK 0 rev. · NOK −33,000 profit

ØVRE NESBYGDA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØVRE NESBYGDA AS

Who owns ØVRE NESBYGDA AS?

KNIVEÅSEN AS is the largest registered owner, with 100.0%.

What is the revenue of ØVRE NESBYGDA AS?

ØVRE NESBYGDA AS had revenue of NOK 0 in 2025.

Where is ØVRE NESBYGDA AS based?

ØVRE NESBYGDA AS has its business address in Drammen.

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

Report a problem

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