BIZTRAC BETA
Non-specialised wholesale trade

SIKKERHETSAGENTUR AS

Org. no. 970891048 Limited company (AS) Nord-Fron Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK −293,000
Equity NOK 224,000
Incorporated 1994
Share capital NOK 100,000

Signals

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

SIKKERHETSAGENTUR AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 970891048. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 1994. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel og tjenesteyting og annet som naturlig faller inn under virksomheten.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK −293,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK −293,000
Equity
NOK 224,000
Est. value
NOK 983,000

Financial health · 2024

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

Who owns SIKKERHETSAGENTUR AS?

FORRELØKKEN HOLDING AS
SIKKERHETSAGENTUR AS
NOK 3.6m rev. · NOK −293,000 profit

SIKKERHETSAGENTUR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIKKERHETSAGENTUR AS

Who owns SIKKERHETSAGENTUR AS?

FORRELØKKEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SIKKERHETSAGENTUR AS?

SIKKERHETSAGENTUR AS had revenue of NOK 3.6m in 2024.

Who is the general manager of SIKKERHETSAGENTUR AS?

Jørgen Forreløkken is registered as general manager of SIKKERHETSAGENTUR AS.

Where is SIKKERHETSAGENTUR AS based?

SIKKERHETSAGENTUR AS has its business address in Vinstra.

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.