BIZTRAC BETA
COMPANY REGISTER PROFILE
928117847 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

DEEP EARNING AS

Org. no. 928117847 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 194,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

DEEP EARNING AS is registered as a limited company in Oslo, Oslo with organisation number 928117847. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Holdingselskap.”.

Key figures · 2024

Operating profit
NOK −14,000
Equity
NOK 194,000
Est. value
NOK 502,000

Financial health · 2024

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

Who owns DEEP EARNING AS?

No shareholders are registered for DEEP EARNING AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does DEEP EARNING AS own?

DEEP EARNING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DEEP EARNING AS

Where is DEEP EARNING AS based?

DEEP EARNING AS has its business address in Oslo.

Property

Business address c/o Thea Knudsen Agathe Grøndahls gate 44, 0478 Oslo
Cadastral unit 301-224/22/0/0
Building Tomannsbolig, vertikal · 3 units

8 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.