BIZTRAC BETA
Rental and operating of own or leased real estate

JFP EIENDOM AS

Org. no. 922424152 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 894,000
Operating profit NOK 366,000
Equity NOK −817,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

JFP EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922424152. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eiendomsutvikling, herunder utleie og drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 894,000 in revenue and NOK 366,000 in operating profit.

Key figures · 2025

Revenue
NOK 894,000
Operating profit
NOK 366,000
Equity
NOK −817,000
Est. value
NOK 2.5m

Financial health · 2024

Liquidity
2.50
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-7.4%
Weak
Equity as a share of total capital

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

Who owns JFP EIENDOM AS?

OTEGO HOLDING AB
JFP EIENDOM AS
NOK 894,000 rev. · NOK 366,000 profit

JFP EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JFP EIENDOM AS own?

JFP EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JFP EIENDOM AS

Who owns JFP EIENDOM AS?

OTEGO HOLDING AB is the largest registered owner, with 51.0%.

What is the revenue of JFP EIENDOM AS?

JFP EIENDOM AS had revenue of NOK 894,000 in 2025.

Where is JFP EIENDOM AS based?

JFP EIENDOM AS has its business address in Trondheim.

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.