BIZTRAC BETA
Buying and selling of own real estate

JULSETH EIENDOM AS

Org. no. 933898237 Limited company (AS) Stjørdal Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −26,000
Equity NOK −2,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−26k kr).

JULSETH EIENDOM AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 933898237. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utleie og salg av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −26,000
Equity
NOK −2,000

Financial health · 2025

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

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

Who owns JULSETH EIENDOM AS?

OLE HÅKON JULSETH
JULSETH EIENDOM AS
NOK 0 rev. · NOK −26,000 profit

JULSETH EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about JULSETH EIENDOM AS

Who owns JULSETH EIENDOM AS?

OLE HÅKON JULSETH is the largest registered owner, with 25.0%.

What is the revenue of JULSETH EIENDOM AS?

JULSETH EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of JULSETH EIENDOM AS?

Brit Heidi Sæther Julseth is registered as general manager of JULSETH EIENDOM AS.

Where is JULSETH EIENDOM AS based?

JULSETH EIENDOM AS has its business address in Elvarli.

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.