BIZTRAC BETA
Combined facilities support activities

VT VAKTMESTER AS

Org. no. 924734469 Limited company (AS) Tønsberg Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 210,000
Operating profit NOK −48,000
Equity NOK 420,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−48k kr).

VT VAKTMESTER AS is registered as a limited company in Tønsberg, Vestfold with organisation number 924734469. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Vaktmestertjenester - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 210,000 in revenue and NOK −48,000 in operating profit.

Key figures · 2024

Revenue
NOK 210,000
Operating profit
NOK −48,000
Equity
NOK 420,000
Est. value
NOK 344,000

Financial health · 2024

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

Who owns VT VAKTMESTER AS?

KAI ARNE AAS
VT VAKTMESTER AS
NOK 210,000 rev. · NOK −48,000 profit

VT VAKTMESTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VT VAKTMESTER AS

Who owns VT VAKTMESTER AS?

KAI ARNE AAS is the largest registered owner, with 100.0%.

What is the revenue of VT VAKTMESTER AS?

VT VAKTMESTER AS had revenue of NOK 210,000 in 2024.

Who is the general manager of VT VAKTMESTER AS?

Kai Arne Aas is registered as general manager of VT VAKTMESTER AS.

Where is VT VAKTMESTER AS based?

VT VAKTMESTER AS has its business address in Tolvsrød.

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.