BIZTRAC BETA
Rental and operating of own or leased real estate

JON BORGE EIENDOM AS

Org. no. 914910854 Limited company (AS) Fredrikstad Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 692,000
Operating profit NOK 208,000
Equity NOK 1.4m
Incorporated 2015
Share capital NOK 30,000

JON BORGE EIENDOM AS is registered as a limited company in Fredrikstad, Østfold with organisation number 914910854. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og drift av fast eiendom og det som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 692,000 in revenue and NOK 208,000 in operating profit.

Key figures · 2025

Revenue
NOK 692,000
Operating profit
NOK 208,000
Equity
NOK 1.4m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns JON BORGE EIENDOM AS?

JON BORGE HOLDING AS
JON BORGE EIENDOM AS
NOK 692,000 rev. · NOK 208,000 profit

JON BORGE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

JON BORGE EIENDOM AS er morselskap for 2 datterselskaper:

Frequently asked questions about JON BORGE EIENDOM AS

Who owns JON BORGE EIENDOM AS?

JON BORGE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JON BORGE EIENDOM AS?

JON BORGE EIENDOM AS had revenue of NOK 692,000 in 2025.

Who is the general manager of JON BORGE EIENDOM AS?

Jon Borge is registered as general manager of JON BORGE EIENDOM AS.

Where is JON BORGE EIENDOM AS based?

JON BORGE EIENDOM AS 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.