biztrac. BETA
COMPANY REGISTER PROFILE
918969721 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other construction installation

ALLSIKRING AS

Org. no. 918969721 Limited company (AS) Tønsberg Incorporated 2017 Active
Revenue 2025 NOK 56.4m
Operating profit NOK 2.3m
Equity NOK 7.7m
Incorporated 2017
Employees 31
Share capital NOK 1.7m

ALLSIKRING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 918969721. The business is classified under other construction installation (NACE 43.240). The company was incorporated in 2017 and has 31 registered employees. Registered share capital is NOK 1.7m, divided into 17000 shares. The company's stated purpose is: “Handel, produksjon, service og konsulentarbeid, samt aksjetegning eller på annen måte delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 56.4m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 56.4m
▲ +0 %
Operating profit
NOK 2.3m
▲ +0 %
Equity
NOK 7.7m
▲ +0 %
Est. value
NOK 10.4m

Financial health · 2025

Liquidity
1.53
Good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
36.2%
Good
Equity as a share of total capital

Who owns ALLSIKRING AS?

ALLSIKRING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ALLSIKRING AS own?

ALLSIKRING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ALLSIKRING AS

Who owns ALLSIKRING AS?

TOJO AS is the largest registered owner, with 32.5%.

What is the revenue of ALLSIKRING AS?

ALLSIKRING AS had revenue of NOK 56.4m in 2025.

Who is the general manager of ALLSIKRING AS?

Espen Lyngvær is registered as general manager of ALLSIKRING AS.

Where is ALLSIKRING AS based?

ALLSIKRING AS has its business address in Barkåker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.