BIZTRAC BETA
Retail sale of electrical household appliances

VIKEN LÅS OG SIKKERHET AS

Org. no. 923399623 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 53.3m
Operating profit NOK 4.4m
Equity NOK 11.8m
Incorporated 2019
Employees 19
Share capital NOK 30,000

VIKEN LÅS OG SIKKERHET AS is registered as a limited company in Drammen, Buskerud with organisation number 923399623. The business is classified under retail sale of electrical household appliances (NACE 47.540). The company was incorporated in 2019 and has 19 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp og salg, samt service av låssystemer for personkunder og bedriftskunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 53.3m in revenue and NOK 4.4m in operating profit.

Key figures · 2025

Revenue
NOK 53.3m
Operating profit
NOK 4.4m
Equity
NOK 11.8m
Est. value
NOK 21.6m

Financial health · 2025

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

Who owns VIKEN LÅS OG SIKKERHET AS?

GLENN EIVIND ELTON
VIKEN LÅS OG SIKKERHET AS
NOK 53.3m rev. · NOK 4.4m profit

VIKEN LÅS OG SIKKERHET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIKEN LÅS OG SIKKERHET AS

Who owns VIKEN LÅS OG SIKKERHET AS?

GLENN EIVIND ELTON is the largest registered owner, with 80.0%.

What is the revenue of VIKEN LÅS OG SIKKERHET AS?

VIKEN LÅS OG SIKKERHET AS had revenue of NOK 53.3m in 2025.

Who is the general manager of VIKEN LÅS OG SIKKERHET AS?

Glenn Eivind Elton is registered as general manager of VIKEN LÅS OG SIKKERHET AS.

Where is VIKEN LÅS OG SIKKERHET AS based?

VIKEN LÅS OG SIKKERHET AS has its business address in Drammen.

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.