BIZTRAC BETA
Rental and operating of own or leased real estate

J U EIENDOM AS

Org. no. 987774886 Limited company (AS) Kongsberg Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 148,000
Operating profit NOK 76,000
Equity NOK 12.1m
Incorporated 2005
Share capital NOK 31,000

J U EIENDOM AS is registered as a limited company in Kongsberg, Buskerud with organisation number 987774886. 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 31,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, håndtverkstjenester, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 148,000 in revenue and NOK 76,000 in operating profit.

Key figures · 2025

Revenue
NOK 148,000
Operating profit
NOK 76,000
Equity
NOK 12.1m
Est. value
NOK 8.5m

Financial health · 2025

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

Who owns J U EIENDOM AS?

JARLE UELAND
J U EIENDOM AS
NOK 148,000 rev. · NOK 76,000 profit

J U EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does J U EIENDOM AS own?

J U EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about J U EIENDOM AS

Who owns J U EIENDOM AS?

JARLE UELAND is the largest registered owner, with 100.0%.

What is the revenue of J U EIENDOM AS?

J U EIENDOM AS had revenue of NOK 148,000 in 2025.

Who is the general manager of J U EIENDOM AS?

Jarle Ueland is registered as general manager of J U EIENDOM AS.

Where is J U EIENDOM AS based?

J U EIENDOM AS has its business address in Kongsberg.

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.