BIZTRAC BETA
Rental and operating of own or leased real estate

DRAMMENSVEIEN 85 KONGSBERG AS

Org. no. 915147933 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 3.4m
Equity NOK 15.7m
Incorporated 2015
Share capital NOK 7.2m

DRAMMENSVEIEN 85 KONGSBERG AS is registered as a limited company in Oslo, Oslo with organisation number 915147933. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 7.2m, divided into 7246548 shares. The company's stated purpose is: “Investering i fast eiendom, herunder utleie, drift, kjøp og salg, samt investering i aksjer og andre verdipapirer, herunder aktiv deltagelse i andre selskaper. I tillegg kommer annen nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 3.4m in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 3.4m
Equity
NOK 15.7m
Est. value
NOK 17.0m

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.8%
Very good
Equity as a share of total capital

Who owns DRAMMENSVEIEN 85 KONGSBERG AS?

RAGDE EIENDOM AS
DRAMMENSVEIEN 85 KONGSBERG AS
NOK 4.4m rev. · NOK 3.4m profit

DRAMMENSVEIEN 85 KONGSBERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRAMMENSVEIEN 85 KONGSBERG AS

Who owns DRAMMENSVEIEN 85 KONGSBERG AS?

RAGDE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of DRAMMENSVEIEN 85 KONGSBERG AS?

DRAMMENSVEIEN 85 KONGSBERG AS had revenue of NOK 4.4m in 2025.

Where is DRAMMENSVEIEN 85 KONGSBERG AS based?

DRAMMENSVEIEN 85 KONGSBERG AS has its business address in Oslo.

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.