biztrac. BETA
COMPANY REGISTER PROFILE
930053554 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

LOCKERT HOLDING AS

Org. no. 930053554 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −109,000
Equity NOK 750,000
Incorporated 2022
Share capital NOK 750,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−109k kr).

LOCKERT HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 930053554. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 750,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av aksjer og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −109,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −109,000
Equity
NOK 750,000
Est. value
NOK 684,000

Financial health · 2025

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
27.5%
Very good
Return on total assets
Solidity
40.2%
Very good
Equity as a share of total capital

Who owns LOCKERT HOLDING AS?

LOCKERT HOLDING AS
NOK 0 rev. · NOK −109,000 profit

LOCKERT HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LOCKERT HOLDING AS own?

LOCKERT HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LOCKERT HOLDING AS

Who owns LOCKERT HOLDING AS?

Espen Lockert is the largest registered owner, with 100.0%.

What is the revenue of LOCKERT HOLDING AS?

LOCKERT HOLDING AS had revenue of NOK 0 in 2025.

Where is LOCKERT HOLDING AS based?

LOCKERT HOLDING AS has its business address in Hafrsfjord.

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.