BIZTRAC BETA
COMPANY REGISTER PROFILE
816943442 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

JE JENSEN HOLDING AS

Org. no. 816943442 Limited company (AS) Nittedal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 10.9m
Incorporated 2016
Share capital NOK 107,000

Signals

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

JE JENSEN HOLDING AS is registered as a limited company in Nittedal, Akershus with organisation number 816943442. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 107,000, divided into 107111 shares. The company's stated purpose is: “Investeringer i aksjer, eiendom og alt som derved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 10.9m
Est. value
NOK 7.2m

Financial health · 2025

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

Who owns JE JENSEN HOLDING AS?

JENS EGIL JENSEN
JE JENSEN HOLDING AS
NOK 0 rev. · NOK −16,000 profit

JE JENSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JE JENSEN HOLDING AS own?

JE JENSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JE JENSEN HOLDING AS

Who owns JE JENSEN HOLDING AS?

JENS EGIL JENSEN is the largest registered owner, with 100.0%.

What is the revenue of JE JENSEN HOLDING AS?

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

Where is JE JENSEN HOLDING AS based?

JE JENSEN HOLDING AS has its business address in Nittedal.

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.