BIZTRAC BETA
COMPANY REGISTER PROFILE
992162376 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Manufacture of locks and hinges

ASKIM LÅSSERVICE AS

Org. no. 992162376 Limited company (AS) Indre Østfold Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 23,000
Equity NOK 569,000
Incorporated 2008
Share capital NOK 100,000

ASKIM LÅSSERVICE AS is registered as a limited company in Indre Østfold, Østfold with organisation number 992162376. The business is classified under manufacture of locks and hinges (NACE 25.620). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av tjenester og produkter tilknyttet vakthold og sikring av objekter, investeringer og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 23,000 in operating profit.

Former names: MR. TRAFFIC NORGE AS, SUPERDAY AS, PASOPVEIEN AS, SUPERDAY AIR AND SPACE AS, EXITUS AS

Key figures · 2025

Revenue
NOK 1.9m
▼ −10 %
Operating profit
NOK 23,000
▲ +116 %
Equity
NOK 569,000
▼ −4 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
2.94
Very good
Current assets ÷ current liabilities
Profitability
1.9%
Weak
Return on total assets
Solidity
42.5%
Very good
Equity as a share of total capital

Who owns ASKIM LÅSSERVICE AS?

ASKIM LÅSSERVICE AS
NOK 1.9m rev. · NOK 23,000 profit

ASKIM LÅSSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASKIM LÅSSERVICE AS

Who owns ASKIM LÅSSERVICE AS?

GLENN ROBERT EILERTSEN is the largest registered owner, with 100.0%.

What is the revenue of ASKIM LÅSSERVICE AS?

ASKIM LÅSSERVICE AS had revenue of NOK 1.9m in 2025.

Where is ASKIM LÅSSERVICE AS based?

ASKIM LÅSSERVICE AS has its business address in Askim.

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

Report a problem

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