BIZTRAC BETA
Rental and operating of own or leased real estate

JEDI EIENDOM AS

Org. no. 988622168 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 28,000
Operating profit NOK 13,000
Equity NOK −168,000
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−168k kr).

JEDI EIENDOM AS is registered as a limited company in Kristiansand, Agder with organisation number 988622168. 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 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av eiendom, utvikling og utleie av eiendom og alt hva som står i forbindelse med dette. Selskapet kan eie andre selskaper helt eller delvis.”. The most recent filed accounts, for the 2025 financial year, show NOK 28,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2025

Revenue
NOK 28,000
Operating profit
NOK 13,000
Equity
NOK −168,000
Est. value
NOK 86,000

Financial health · 2025

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns JEDI EIENDOM AS?

LUNDSLETTA 31 AS
JEDI EIENDOM AS
NOK 28,000 rev. · NOK 13,000 profit

JEDI EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JEDI EIENDOM AS

Who owns JEDI EIENDOM AS?

LUNDSLETTA 31 AS is the largest registered owner, with 100.0%.

What is the revenue of JEDI EIENDOM AS?

JEDI EIENDOM AS had revenue of NOK 28,000 in 2025.

Where is JEDI EIENDOM AS based?

JEDI EIENDOM AS has its business address in Kristiansand S.

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.