BIZTRAC BETA
COMPANY REGISTER PROFILE
920193552 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

JE ERIKSEN AS

Org. no. 920193552 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 270,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

JE ERIKSEN AS is registered as a limited company in Oslo, Oslo with organisation number 920193552. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie og investere i aksjer, samt deltagelse i andre selskaper med virksomhet innen informasjonsteknologi og der tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 270,000
Est. value
NOK 246,000

Financial health · 2025

Liquidity
Not available
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 ERIKSEN AS?

JON EGIL ERIKSEN
JE ERIKSEN AS
NOK 0 rev. · NOK −1,000 profit

JE ERIKSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JE ERIKSEN AS own?

JE ERIKSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JE ERIKSEN AS

Who owns JE ERIKSEN AS?

JON EGIL ERIKSEN is the largest registered owner, with 100.0%.

What is the revenue of JE ERIKSEN AS?

JE ERIKSEN AS had revenue of NOK 0 in 2025.

Where is JE ERIKSEN AS based?

JE ERIKSEN AS has its business address in Oslo.

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.