BIZTRAC BETA
Rental and operating of own or leased real estate

JE FOSSHAUG HOLDING AS

Org. no. 924045809 Limited company (AS) Ullensaker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −86,000
Equity NOK 17.1m
Incorporated 2019
Share capital NOK 60,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−86k kr).

JE FOSSHAUG HOLDING AS is registered as a limited company in Ullensaker, Akershus with organisation number 924045809. 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 60,000, divided into 30 shares. The company's stated purpose is: “Delta og investere i andre foretak og hva dermed er forbundet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −86,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −86,000
Equity
NOK 17.1m
Est. value
NOK 12.7m

Financial health · 2025

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

Who owns JE FOSSHAUG HOLDING AS?

JAN EGIL FOSSHAUG
JE FOSSHAUG HOLDING AS
NOK 0 rev. · NOK −86,000 profit

JE FOSSHAUG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JE FOSSHAUG HOLDING AS

Who owns JE FOSSHAUG HOLDING AS?

JAN EGIL FOSSHAUG is the largest registered owner, with 100.0%.

What is the revenue of JE FOSSHAUG HOLDING AS?

JE FOSSHAUG HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of JE FOSSHAUG HOLDING AS?

Jan Egil Fosshaug is registered as general manager of JE FOSSHAUG HOLDING AS.

Where is JE FOSSHAUG HOLDING AS based?

JE FOSSHAUG HOLDING 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.