BIZTRAC BETA
COMPANY REGISTER PROFILE
935024005 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

AGARDH 639 AS

Org. no. 935024005 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Equity NOK 31,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AGARDH 639 AS is registered as a limited company in Oslo, Oslo with organisation number 935024005. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i andre selskap og forestå tilhørende aktiviteter.”.

Key figures · 2025

Equity
NOK 31,000
Est. value
NOK 24,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AGARDH 639 AS?

AGARDH 639 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AGARDH 639 AS

Who owns AGARDH 639 AS?

AGARDH HOLDING AS is the largest registered owner, with 100.0%.

Where is AGARDH 639 AS based?

AGARDH 639 AS has its business address in Oslo.

Property

Business address c/o Advokatfirmaet Haavind AS Haakon VIIs gate 10, 0161 Oslo
Cadastral unit 301-209/133/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

126 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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