biztrac. BETA
COMPANY REGISTER PROFILE
826838892 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Wholesale of hardware, plumbing and heating equipment and supplies

LOCKY AS

Org. no. 826838892 Limited company (AS) Sokndal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 7.9m
Operating profit NOK 1.3m
Equity NOK 158,000
Incorporated 2021
Employees 5
Share capital NOK 50,000

LOCKY AS is registered as a limited company in Sokndal, Rogaland with organisation number 826838892. The business is classified under wholesale of hardware, plumbing and heating equipment and supplies (NACE 46.840). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Selge og levere adgangskontrollsystemer til kontorer, borettslag, butikklokaler, boder og tilhørende virksomheter og bransjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.9m in revenue and NOK 1.3m in operating profit.

Former names: QUICKSIGN AS

Key figures · 2025

Revenue
NOK 7.9m
▲ +25 %
Operating profit
NOK 1.3m
▲ +7054 %
Equity
NOK 158,000
▲ +106 %
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
0.96
Weak
Current assets ÷ current liabilities
Profitability
52.5%
Very good
Return on total assets
Solidity
5.9%
Weak
Equity as a share of total capital

Who owns LOCKY AS?

LOCKY AS
NOK 7.9m rev. · NOK 1.3m profit

LOCKY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOCKY AS

Who owns LOCKY AS?

THUNDER TECHNOLOGY AS is the largest registered owner, with 100.0%.

What is the revenue of LOCKY AS?

LOCKY AS had revenue of NOK 7.9m in 2025.

Who is the general manager of LOCKY AS?

Kai Tønder is registered as general manager of LOCKY AS.

Where is LOCKY AS based?

LOCKY AS has its business address in Hauge I Dalane.

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.