biztrac. BETA
COMPANY REGISTER PROFILE
932950782 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

DIESETH EIENDOM AS

Org. no. 932950782 Limited company (AS) Drammen Incorporated 2023 Active
Revenue 2025 NOK 2.1m
Operating profit NOK 66,000
Equity NOK 12.8m
Incorporated 2023
Share capital NOK 5.1m

DIESETH EIENDOM AS is registered as a limited company in Drammen, Buskerud with organisation number 932950782. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 5.1m, divided into 100 shares. The company's stated purpose is: “Kjøpe, selge, eie, leie ut, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 66,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
▲ +171 %
Operating profit
NOK 66,000
▲ +107 %
Equity
NOK 12.8m
▲ +1600 %
Est. value
NOK 10.4m

Financial health · 2025

Liquidity
7.82
Very good
Current assets ÷ current liabilities
Profitability
0.1%
Not satisfactory
Return on total assets
Solidity
20.1%
Good
Equity as a share of total capital

Who owns DIESETH EIENDOM AS?

DIESETH EIENDOM AS
NOK 2.1m rev. · NOK 66,000 profit

DIESETH EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DIESETH EIENDOM AS

Who owns DIESETH EIENDOM AS?

CDAC HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of DIESETH EIENDOM AS?

DIESETH EIENDOM AS had revenue of NOK 2.1m in 2025.

Who is the general manager of DIESETH EIENDOM AS?

Julie Dieseth-Tjessem is registered as general manager of DIESETH EIENDOM AS.

Where is DIESETH EIENDOM AS based?

DIESETH EIENDOM 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.