BIZTRAC BETA
COMPANY REGISTER PROFILE
936239773 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

LAKWJ AS

Org. no. 936239773 Limited company (AS) Øksnes Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −19,000
Equity NOK 100,000
Incorporated 2025
Share capital NOK 100,000

Signals

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

LAKWJ AS is registered as a limited company in Øksnes, Nordland with organisation number 936239773. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 100,000, divided into 200000 shares. The company's stated purpose is: “Investering i aksjer og andre finansielle eiendeler.”.

Key figures · 2025

Operating profit
NOK −19,000
Equity
NOK 100,000
Est. value
NOK 102.9m

Financial health · 2025

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.4%
Not satisfactory
Equity as a share of total capital

Who owns LAKWJ AS?

LAKWJ AS
· NOK −19,000 profit

LAKWJ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LAKWJ AS own?

LAKWJ AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LAKWJ AS

Who owns LAKWJ AS?

KYST-REVISJON AS is the largest registered owner, with 100.0%.

Where is LAKWJ AS based?

LAKWJ AS has its business address in Alsvåg.

Property

Business address Laksraveien 45, 8432 Alsvåg
Cadastral unit 1868-81/44/0/0
Building Enebolig · 1 unit

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.