BIZTRAC BETA
Combined facilities support activities

VAKTMESTERDRIFT AS

Org. no. 984913524 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 12.4m
Operating profit NOK 1.1m
Equity NOK 4.8m
Incorporated 2002
Employees 22
Share capital NOK 120,000

VAKTMESTERDRIFT AS is registered as a limited company in Oslo, Oslo with organisation number 984913524. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2002 and has 22 registered employees. Registered share capital is NOK 120,000, divided into 120 shares. The company's stated purpose is: “Forvaltning og teknisk drift av fast eiendom og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.4m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 12.4m
Operating profit
NOK 1.1m
Equity
NOK 4.8m
Est. value
NOK 7.5m

Financial health · 2024

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
56.2%
Very good
Equity as a share of total capital

Who owns VAKTMESTERDRIFT AS?

TOM RIISE
VAKTMESTERDRIFT AS
NOK 12.4m rev. · NOK 1.1m profit

VAKTMESTERDRIFT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VAKTMESTERDRIFT AS own?

VAKTMESTERDRIFT AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VAKTMESTERDRIFT AS

Who owns VAKTMESTERDRIFT AS?

TOM RIISE is the largest registered owner, with 66.7%.

What is the revenue of VAKTMESTERDRIFT AS?

VAKTMESTERDRIFT AS had revenue of NOK 12.4m in 2024.

Who is the general manager of VAKTMESTERDRIFT AS?

Tom Riise is registered as general manager of VAKTMESTERDRIFT AS.

Where is VAKTMESTERDRIFT AS based?

VAKTMESTERDRIFT 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.