biztrac. BETA
COMPANY REGISTER PROFILE
993966606 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

LOCKSLEY INVEST AS

Org. no. 993966606 Limited company (AS) Larvik Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 1.0m
Equity NOK 3.8m
Incorporated 2009
Share capital NOK 360,000

LOCKSLEY INVEST AS is registered as a limited company in Larvik, Vestfold with organisation number 993966606. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 360,000, divided into 360 shares. The company's stated purpose is: “Kjøp salg av eiendommer og eiendomsutvikling, herunder deltagelse i andre selskaper, samt annen virksomhet som naturlig faller inn under dette. Import og eksport samt handelsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 1.0m in operating profit.

Former names: S.JOHNSEN EIENDOM AS, K. JOHNSEN EIENDOM AS

Key figures · 2025

Revenue
NOK 3.3m
▲ +94 %
Operating profit
NOK 1.0m
▲ +91 %
Equity
NOK 3.8m
▲ +2 %
Est. value
NOK 4.0m

Financial health · 2025

Liquidity
1.71
Good
Current assets ÷ current liabilities
Profitability
14.7%
Good
Return on total assets
Solidity
48.0%
Very good
Equity as a share of total capital

Who owns LOCKSLEY INVEST AS?

LOCKSLEY INVEST AS
NOK 3.3m rev. · NOK 1.0m profit

LOCKSLEY INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOCKSLEY INVEST AS

Who owns LOCKSLEY INVEST AS?

VESTERVIK AS is the largest registered owner, with 100.0%.

What is the revenue of LOCKSLEY INVEST AS?

LOCKSLEY INVEST AS had revenue of NOK 3.3m in 2025.

Where is LOCKSLEY INVEST AS based?

LOCKSLEY INVEST AS has its business address in Larvik.

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.