BIZTRAC BETA
Accounting and bookkeeping

ORBIT CONSULTING AS

Org. no. 934438450 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −2
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

ORBIT CONSULTING AS is registered as a limited company in Oslo, Oslo with organisation number 934438450. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Orbit Consulting tilbyr profesjonelt tjeneste innenfor regnskap, bokføring, oppstart av selskap i Norge, strategiske råd, løsninger og veiledning innen økonomistyring, budsjettering, skatt, lønn, investeringer og andre økonomiske områder.”.

Key figures · 2024

Operating profit
NOK −2
Equity
NOK 24,000
Est. value
NOK 39,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 ORBIT CONSULTING AS?

IMAN ISMAEL ELMI
ORBIT CONSULTING AS
· NOK −2 profit

ORBIT CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ORBIT CONSULTING AS own?

ORBIT CONSULTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ORBIT CONSULTING AS

Who owns ORBIT CONSULTING AS?

IMAN ISMAEL ELMI is the largest registered owner, with 100.0%.

Who is the general manager of ORBIT CONSULTING AS?

Iman Ismael Elmi is registered as general manager of ORBIT CONSULTING AS.

Where is ORBIT CONSULTING AS based?

ORBIT CONSULTING 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.