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

ARGENTI FODINÆ AS

Org. no. 926019635 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 498,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

ARGENTI FODINÆ AS is registered as a limited company in Bærum, Akershus with organisation number 926019635. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering og forvaltning av kapital, samt alt som naturlig tilhører dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 498,000
Est. value
NOK 585,000

Financial health · 2025

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

Who owns ARGENTI FODINÆ AS?

MORTEN WEBER BERGESEN
ARGENTI FODINÆ AS
NOK 0 rev. · NOK −7,000 profit

ARGENTI FODINÆ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ARGENTI FODINÆ AS own?

ARGENTI FODINÆ AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ARGENTI FODINÆ AS

Who owns ARGENTI FODINÆ AS?

MORTEN WEBER BERGESEN is the largest registered owner, with 100.0%.

What is the revenue of ARGENTI FODINÆ AS?

ARGENTI FODINÆ AS had revenue of NOK 0 in 2025.

Where is ARGENTI FODINÆ AS based?

ARGENTI FODINÆ AS has its business address in Haslum.

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.