biztrac. BETA
COMPANY REGISTER PROFILE
992643404 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other investment companies, except captive companies

ARGENTUM NORDIC PEP 1 AS

Org. no. 992643404 Limited company (AS) Bergen Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 36.1m
Operating profit NOK 36.0m
Equity NOK 19.5m
Incorporated 2008
Share capital NOK 100,000

ARGENTUM NORDIC PEP 1 AS is registered as a limited company in Bergen, Vestland with organisation number 992643404. The business is classified under other investment companies, except captive companies (NACE 64.312). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Investeringsselskap og å delta i selskaper med samme formål, samt annen virksomhet som dertil hører ved.”. The most recent filed accounts, for the 2025 financial year, show NOK 36.1m in revenue and NOK 36.0m in operating profit.

Former names: STARTFASE 320 AS

Key figures · 2025

Revenue
NOK 36.1m
▲ +543 %
Operating profit
NOK 36.0m
▲ +540 %
Equity
NOK 19.5m
▼ −16 %
Est. value
NOK 53.3m

Financial health · 2025

Liquidity
20.01
Very good
Current assets ÷ current liabilities
Profitability
163.8%
Very good
Return on total assets
Solidity
95.0%
Very good
Equity as a share of total capital

Who owns ARGENTUM NORDIC PEP 1 AS?

ARGENTUM NORDIC PEP 1 AS
NOK 36.1m rev. · NOK 36.0m profit

ARGENTUM NORDIC PEP 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARGENTUM NORDIC PEP 1 AS

Who owns ARGENTUM NORDIC PEP 1 AS?

ARGENTUM FONDSINVESTERINGER AS is the largest registered owner, with 100.0%.

What is the revenue of ARGENTUM NORDIC PEP 1 AS?

ARGENTUM NORDIC PEP 1 AS had revenue of NOK 36.1m in 2025.

Where is ARGENTUM NORDIC PEP 1 AS based?

ARGENTUM NORDIC PEP 1 AS has its business address in Bergen.

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.