biztrac. BETA
COMPANY REGISTER PROFILE
931446134 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

J3EA HOLDING AS

Org. no. 931446134 Limited company (AS) Stavanger Incorporated 2023 Active
Revenue 2025 NOK 875,000
Operating profit NOK 818,000
Equity NOK 154.0m
Incorporated 2023
Share capital NOK 30,000

J3EA HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 931446134. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 12000 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 875,000 in revenue and NOK 818,000 in operating profit.

Key figures · 2025

Revenue
NOK 875,000
Operating profit
NOK 818,000
▲ +3523 %
Equity
NOK 154.0m
▼ −4 %
Est. value
NOK 83.8m

Financial health · 2025

Liquidity
0.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
0.5%
Not satisfactory
Return on total assets
Solidity
95.6%
Very good
Equity as a share of total capital

Who owns J3EA HOLDING AS?

J3EA HOLDING AS
NOK 875,000 rev. · NOK 818,000 profit

J3EA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does J3EA HOLDING AS own?

J3EA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about J3EA HOLDING AS

Who owns J3EA HOLDING AS?

Lasse Oddmar Andresen is the largest registered owner, with 100.0%.

What is the revenue of J3EA HOLDING AS?

J3EA HOLDING AS had revenue of NOK 875,000 in 2025.

Who is the general manager of J3EA HOLDING AS?

Lasse Oddmar Andresen is registered as general manager of J3EA HOLDING AS.

Where is J3EA HOLDING AS based?

J3EA HOLDING AS has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.