BIZTRAC BETA
Investigation and private security activities

TELEMARK VAKTSELSKAP AS

Org. no. 990728283 Limited company (AS) Midt-Telemark Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 5.4m
Operating profit NOK 76,000
Equity NOK 1.6m
Incorporated 2006
Employees 12
Share capital NOK 140,000

TELEMARK VAKTSELSKAP AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 990728283. The business is classified under investigation and private security activities (NACE 80.010). The company was incorporated in 2006 and has 12 registered employees. Registered share capital is NOK 140,000, divided into 140 shares. The company's stated purpose is: “Drift av vaktselskap og hva som står i en naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.4m in revenue and NOK 76,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.4m
Operating profit
NOK 76,000
Equity
NOK 1.6m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns TELEMARK VAKTSELSKAP AS?

TEAM SECURITY AS
TELEMARK VAKTSELSKAP AS
NOK 5.4m rev. · NOK 76,000 profit

TELEMARK VAKTSELSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TELEMARK VAKTSELSKAP AS

Who owns TELEMARK VAKTSELSKAP AS?

TEAM SECURITY AS is the largest registered owner, with 90.0%.

What is the revenue of TELEMARK VAKTSELSKAP AS?

TELEMARK VAKTSELSKAP AS had revenue of NOK 5.4m in 2024.

Who is the general manager of TELEMARK VAKTSELSKAP AS?

Thomas Skindalen Moen is registered as general manager of TELEMARK VAKTSELSKAP AS.

Where is TELEMARK VAKTSELSKAP AS based?

TELEMARK VAKTSELSKAP AS has its business address in Gvarv.

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.