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

MOSER AS

Org. no. 935997453 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

MOSER AS is registered as a limited company in Oslo, Oslo with organisation number 935997453. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i verdipapirer.”.

Key figures · 2025

Operating profit
NOK −3,000
Equity
NOK 23,000
Est. value
NOK 27,000

Financial health · 2025

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

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

Who owns MOSER AS?

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

Which companies does MOSER AS own?

MOSER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MOSER AS

Where is MOSER AS based?

MOSER AS has its business address in Oslo.

Property

Business address Vogts gate 54, 0477 Oslo
Cadastral unit 301-225/363/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 12 units

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