BIZTRAC BETA
Non-specialised wholesale trade

SIKKER.NO AS

Org. no. 975871134 Limited company (AS) Sortland Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 265,000
Equity NOK 107,000
Incorporated 1995
Share capital NOK 100,000

SIKKER.NO AS is registered as a limited company in Sortland, Nordland with organisation number 975871134. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 1995. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av varer og tjenester innenfor området brann- og sikkerhetsinstallasjoner, og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 265,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 265,000
Equity
NOK 107,000
Est. value
NOK 999,000

Financial health · 2025

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

Who owns SIKKER.NO AS?

PER-INGVAR JAKOBSEN
SIKKER.NO AS
NOK 3.2m rev. · NOK 265,000 profit

SIKKER.NO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIKKER.NO AS

Who owns SIKKER.NO AS?

PER-INGVAR JAKOBSEN is the largest registered owner, with 100.0%.

What is the revenue of SIKKER.NO AS?

SIKKER.NO AS had revenue of NOK 3.2m in 2025.

Who is the general manager of SIKKER.NO AS?

Per-Ingvar Jakobsen is registered as general manager of SIKKER.NO AS.

Where is SIKKER.NO AS based?

SIKKER.NO AS has its business address in Sortland.

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.