BIZTRAC BETA
Rental and operating of own or leased real estate

JØLSEN EIENDOM 2 AS

Org. no. 925366439 Limited company (AS) Ullensaker Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 200,000
Operating profit NOK 178,000
Equity NOK 7.2m
Incorporated 2020
Share capital NOK 60,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JØLSEN EIENDOM 2 AS is registered as a limited company in Ullensaker, Akershus with organisation number 925366439. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 3000 shares. The company's stated purpose is: “Kjøp, salg, utvikling, utbygging, forvaltning og utleie av fast eiendom, samt hva naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 200,000 in revenue and NOK 178,000 in operating profit.

Key figures · 2024

Revenue
NOK 200,000
Operating profit
NOK 178,000
Equity
NOK 7.2m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns JØLSEN EIENDOM 2 AS?

SIGURD FURULUND HOLDING AS
JØLSEN EIENDOM 2 AS
NOK 200,000 rev. · NOK 178,000 profit

JØLSEN EIENDOM 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JØLSEN EIENDOM 2 AS

Who owns JØLSEN EIENDOM 2 AS?

SIGURD FURULUND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JØLSEN EIENDOM 2 AS?

JØLSEN EIENDOM 2 AS had revenue of NOK 200,000 in 2024.

Where is JØLSEN EIENDOM 2 AS based?

JØLSEN EIENDOM 2 AS has its business address in Jessheim.

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.