BIZTRAC BETA
Uoppgitt

ATHOMSTART INVEST 999 AS

Org. no. 934524020 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2024
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.

ATHOMSTART INVEST 999 AS is registered as a limited company in Oslo, Oslo with organisation number 934524020. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Handel med og investering i fast eiendom, verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 35,000

Financial health · 2024

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 ATHOMSTART INVEST 999 AS?

ADVOKATFIRMAET THOMMESSEN AS
ATHOMSTART INVEST 999 AS
NOK 0 rev. · NOK 0 profit

ATHOMSTART INVEST 999 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ATHOMSTART INVEST 999 AS

Who owns ATHOMSTART INVEST 999 AS?

ADVOKATFIRMAET THOMMESSEN AS is the largest registered owner, with 100.0%.

What is the revenue of ATHOMSTART INVEST 999 AS?

ATHOMSTART INVEST 999 AS had revenue of NOK 0 in 2024.

Where is ATHOMSTART INVEST 999 AS based?

ATHOMSTART INVEST 999 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.