BIZTRAC BETA
Security activities n.e.c.

SOLØR SIKKERHET AS

Org. no. 813066432 Limited company (AS) Våler Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 352,000
Operating profit NOK 68,000
Equity NOK 122,000
Incorporated 2014
Share capital NOK 30,000

SOLØR SIKKERHET AS is registered as a limited company in Våler, Innlandet with organisation number 813066432. The business is classified under security activities n.e.c. (NACE 80.090). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg og montering av varslingsanlegg, vaktmestertjenester, varetransport og vaktvirksomhet samt alt som har naturlig sammenheng med dette. Selskapet kan også drive med kjøp og salg av aksjer og kunne ha eierandeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 352,000 in revenue and NOK 68,000 in operating profit.

Key figures · 2024

Revenue
NOK 352,000
Operating profit
NOK 68,000
Equity
NOK 122,000
Est. value
NOK 299,000

Financial health · 2024

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

Who owns SOLØR SIKKERHET AS?

PER ROGER BERGET
SOLØR SIKKERHET AS
NOK 352,000 rev. · NOK 68,000 profit

SOLØR SIKKERHET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLØR SIKKERHET AS

Who owns SOLØR SIKKERHET AS?

PER ROGER BERGET is the largest registered owner, with 100.0%.

What is the revenue of SOLØR SIKKERHET AS?

SOLØR SIKKERHET AS had revenue of NOK 352,000 in 2024.

Who is the general manager of SOLØR SIKKERHET AS?

Per Roger Berget is registered as general manager of SOLØR SIKKERHET AS.

Where is SOLØR SIKKERHET AS based?

SOLØR SIKKERHET AS has its business address in Braskereidfoss.

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.