BIZTRAC BETA
Uoppgitt

LUJEKA AS

Org. no. 932602024 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 64.4m
Operating profit NOK 60.0m
Equity NOK 105.1m
Incorporated 2023
Share capital NOK 63,000

LUJEKA AS is registered as a limited company in Bærum, Akershus with organisation number 932602024. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 63,000, divided into 6259908 shares. The company's stated purpose is: “Kjøp, salg, bebyggelse og drift av fast eiendom og alt som står i forbindelse med dette, videre forvaltning av kapital, investeringer bredt forstått, samt deltakelse i andre selskaper ved aksjetegning og på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 64.4m in revenue and NOK 60.0m in operating profit.

Key figures · 2024

Revenue
NOK 64.4m
Operating profit
NOK 60.0m
Equity
NOK 105.1m
Est. value
NOK 240.7m

Financial health · 2024

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

Who owns LUJEKA AS?

KAROLINE SYNNØVE EGENÆSS WIIG FROGNER
LUJEKA AS
NOK 64.4m rev. · NOK 60.0m profit

LUJEKA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LUJEKA AS own?

LUJEKA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LUJEKA AS

Who owns LUJEKA AS?

KAROLINE SYNNØVE EGENÆSS WIIG FROGNER is the largest registered owner, with 100.0%.

What is the revenue of LUJEKA AS?

LUJEKA AS had revenue of NOK 64.4m in 2024.

Who is the general manager of LUJEKA AS?

Karoline Synnøve Egenæss Wiig Frogner is registered as general manager of LUJEKA AS.

Where is LUJEKA AS based?

LUJEKA AS has its business address in Snarøya.

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.