BIZTRAC BETA
Security activities n.e.c.

VADLA TRYGGHETSBYRÅ AS

Org. no. 983222188 Limited company (AS) Oslo Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −158,000
Equity NOK 449,000
Incorporated 2001
Share capital NOK 100,000

Signals

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

VADLA TRYGGHETSBYRÅ AS is registered as a limited company in Oslo, Oslo with organisation number 983222188. The business is classified under security activities n.e.c. (NACE 80.090). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Tjenesteyting innen fagområdene svinnforebygging, vakt/sikring.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −158,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −158,000
Equity
NOK 449,000
Est. value
NOK 930,000

Financial health · 2024

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

Who owns VADLA TRYGGHETSBYRÅ AS?

RISA VESTFRA AS
VADLA TRYGGHETSBYRÅ AS
NOK 1.1m rev. · NOK −158,000 profit

VADLA TRYGGHETSBYRÅ AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about VADLA TRYGGHETSBYRÅ AS

Who owns VADLA TRYGGHETSBYRÅ AS?

RISA VESTFRA AS is the largest registered owner, with 56.0%.

What is the revenue of VADLA TRYGGHETSBYRÅ AS?

VADLA TRYGGHETSBYRÅ AS had revenue of NOK 1.1m in 2024.

Who is the general manager of VADLA TRYGGHETSBYRÅ AS?

Steinar Vadla Risa is registered as general manager of VADLA TRYGGHETSBYRÅ AS.

Where is VADLA TRYGGHETSBYRÅ AS based?

VADLA TRYGGHETSBYRÅ 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.