BIZTRAC BETA
Combined facilities support activities

TOTEN VAKTMESTERSERVICE AS

Org. no. 925217069 Limited company (AS) Søndre Land Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 92,000
Operating profit NOK 41,000
Equity NOK 4,000
Incorporated 2020
Share capital NOK 50,000

TOTEN VAKTMESTERSERVICE AS is registered as a limited company in Søndre Land, Innlandet with organisation number 925217069. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Vaktmestertjenester og alt som naturlig faller sammen med dette”. The most recent filed accounts, for the 2025 financial year, show NOK 92,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 92,000
Operating profit
NOK 41,000
Equity
NOK 4,000
Est. value
NOK 126,000

Financial health · 2025

Liquidity
0.77
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.0%
Weak
Equity as a share of total capital

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

Who owns TOTEN VAKTMESTERSERVICE AS?

KNUT ØFSTBØ
TOTEN VAKTMESTERSERVICE AS
NOK 92,000 rev. · NOK 41,000 profit

TOTEN VAKTMESTERSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOTEN VAKTMESTERSERVICE AS

Who owns TOTEN VAKTMESTERSERVICE AS?

KNUT ØFSTBØ is the largest registered owner, with 100.0%.

What is the revenue of TOTEN VAKTMESTERSERVICE AS?

TOTEN VAKTMESTERSERVICE AS had revenue of NOK 92,000 in 2025.

Who is the general manager of TOTEN VAKTMESTERSERVICE AS?

Knut Øfstbø is registered as general manager of TOTEN VAKTMESTERSERVICE AS.

Where is TOTEN VAKTMESTERSERVICE AS based?

TOTEN VAKTMESTERSERVICE AS has its business address in Vestsida.

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.