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

KONTORHUSET DRIFT AS

Org. no. 918630511 Limited company (AS) Drammen Incorporated 2017 Active
Revenue 2025 NOK 26.3m
Operating profit NOK 532,000
Equity NOK 5.8m
Incorporated 2017
Share capital NOK 30,000

KONTORHUSET DRIFT AS is registered as a limited company in Drammen, Buskerud with organisation number 918630511. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift og utvikling av kontorhotell, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 26.3m in revenue and NOK 532,000 in operating profit.

Key figures · 2025

Revenue
NOK 26.3m
▼ −3 %
Operating profit
NOK 532,000
▼ −47 %
Equity
NOK 5.8m
▼ −0 %
Est. value
NOK 5.4m

Financial health · 2025

Liquidity
0.32
Not satisfactory
Current assets ÷ current liabilities
Profitability
8.3%
Satisfactory
Return on total assets
Solidity
39.3%
Good
Equity as a share of total capital

Who owns KONTORHUSET DRIFT AS?

KONTORHUSET DRIFT AS
NOK 26.3m rev. · NOK 532,000 profit

KONTORHUSET DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONTORHUSET DRIFT AS

Who owns KONTORHUSET DRIFT AS?

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

What is the revenue of KONTORHUSET DRIFT AS?

KONTORHUSET DRIFT AS had revenue of NOK 26.3m in 2025.

Who is the general manager of KONTORHUSET DRIFT AS?

Trine Maren Skott-Myhre is registered as general manager of KONTORHUSET DRIFT AS.

Where is KONTORHUSET DRIFT AS based?

KONTORHUSET DRIFT 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.