BIZTRAC BETA
Rental and operating of own or leased real estate

LJM AS

Org. no. 989623907 Limited company (AS) Lørenskog Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 26.7m
Operating profit NOK 2.6m
Equity NOK 568.9m
Incorporated 2006
Share capital NOK 1.5m

LJM AS is registered as a limited company in Lørenskog, Akershus with organisation number 989623907. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 1.5m, divided into 106500 shares. The company's stated purpose is: “Foreta investering i og utvikling av verdipapirer, fast eiendom og alt som står i naturlig sammenheng med dette, samt handel med aksjer og verdipapirer og valuta, hvor selskapet kan pantsette sine aktiver i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.7m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 26.7m
Operating profit
NOK 2.6m
Equity
NOK 568.9m
Est. value
NOK 403.8m

Financial health · 2024

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

Who owns LJM AS?

LEIF JØRGEN MOGER
LJM AS
NOK 26.7m rev. · NOK 2.6m profit

LJM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LJM AS own?

LJM AS holds stakes in 50+ companies:

See the full ownership structure →

Frequently asked questions about LJM AS

Who owns LJM AS?

LEIF JØRGEN MOGER is the largest registered owner, with 100.0%.

What is the revenue of LJM AS?

LJM AS had revenue of NOK 26.7m in 2024.

Who is the general manager of LJM AS?

Leif Jørgen Moger is registered as general manager of LJM AS.

Where is LJM AS based?

LJM AS has its business address in Finstadjordet.

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.