BIZTRAC BETA
Rental and operating of own or leased real estate

J.L. EIENDOM A/S

Org. no. 988502588 Limited company (AS) Fredrikstad Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK 357,000
Equity NOK 1.8m
Incorporated 2005
Share capital NOK 200,000

J.L. EIENDOM A/S is registered as a limited company in Fredrikstad, Østfold with organisation number 988502588. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Kjøp og oppføring av egne bygg, utleie av disse samt deltakelse i andre selskap med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK 357,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK 357,000
Equity
NOK 1.8m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns J.L. EIENDOM A/S?

JON EGIL LARSEN
J.L. EIENDOM A/S
NOK 1.4m rev. · NOK 357,000 profit

J.L. EIENDOM A/S has 2 registered shareholders:

All shareholders and roles →

Which companies does J.L. EIENDOM A/S own?

J.L. EIENDOM A/S holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about J.L. EIENDOM A/S

Who owns J.L. EIENDOM A/S?

JON EGIL LARSEN is the largest registered owner, with 50.0%.

What is the revenue of J.L. EIENDOM A/S?

J.L. EIENDOM A/S had revenue of NOK 1.4m in 2024.

Who is the general manager of J.L. EIENDOM A/S?

Jon Egil Larsen is registered as general manager of J.L. EIENDOM A/S.

Where is J.L. EIENDOM A/S based?

J.L. EIENDOM A/S has its business address in Sellebakk.

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.