BIZTRAC BETA
Combined facilities support activities

TB VAKTMESTERSERVICE AS

Org. no. 998906822 Limited company (AS) Kristiansand Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 175,000
Equity NOK 43,000
Incorporated 2012
Share capital NOK 30,000

TB VAKTMESTERSERVICE AS is registered as a limited company in Kristiansand, Agder with organisation number 998906822. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Vaktmesterservice, drift av bygg og eiendom, investeringer i selskap med beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 175,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 175,000
Equity
NOK 43,000
Est. value
NOK 761,000

Financial health · 2024

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

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

Who owns TB VAKTMESTERSERVICE AS?

TOR BIRKELAND
TB VAKTMESTERSERVICE AS
NOK 2.8m rev. · NOK 175,000 profit

TB VAKTMESTERSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TB VAKTMESTERSERVICE AS

Who owns TB VAKTMESTERSERVICE AS?

TOR BIRKELAND is the largest registered owner, with 53.3%.

What is the revenue of TB VAKTMESTERSERVICE AS?

TB VAKTMESTERSERVICE AS had revenue of NOK 2.8m in 2025.

Who is the general manager of TB VAKTMESTERSERVICE AS?

Tor Birkeland is registered as general manager of TB VAKTMESTERSERVICE AS.

Where is TB VAKTMESTERSERVICE AS based?

TB VAKTMESTERSERVICE AS has its business address in Kristiansand S.

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.