BIZTRAC BETA
Buying and selling of own real estate

OVE GJEDDES VEI AS

Org. no. 913406567 Limited company (AS) Kongsberg Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −34,000
Equity NOK −12,000
Incorporated 2014
Share capital NOK 100,000

Signals

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

OVE GJEDDES VEI AS is registered as a limited company in Kongsberg, Buskerud with organisation number 913406567. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, drift, salg, utbygging og utleie av faste eiendommer og herunder hørende virksomhet, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −34,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −34,000
Equity
NOK −12,000

Financial health · 2024

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

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

Who owns OVE GJEDDES VEI AS?

KROKSTAD HANDELSEIENDOM AS
OVE GJEDDES VEI AS
NOK 0 rev. · NOK −34,000 profit

OVE GJEDDES VEI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OVE GJEDDES VEI AS

Who owns OVE GJEDDES VEI AS?

KROKSTAD HANDELSEIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of OVE GJEDDES VEI AS?

OVE GJEDDES VEI AS had revenue of NOK 0 in 2024.

Where is OVE GJEDDES VEI AS based?

OVE GJEDDES VEI AS has its business address in Kongsberg.

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.