BIZTRAC BETA
Computer consultancy and computer facilities management activities

AIM CONSULTING AS

Org. no. 935737699 Limited company (AS) Bømlo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 520,000
Operating profit NOK 153,000
Equity NOK 144,000
Incorporated 2025
Share capital NOK 30,000

AIM CONSULTING AS is registered as a limited company in Bømlo, Vestland with organisation number 935737699. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 520,000 in revenue and NOK 153,000 in operating profit.

Key figures · 2025

Revenue
NOK 520,000
Operating profit
NOK 153,000
Equity
NOK 144,000
Est. value
NOK 753,000

Financial health · 2025

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

Who owns AIM CONSULTING AS?

CHRISTIAN HOPE
AIM CONSULTING AS
NOK 520,000 rev. · NOK 153,000 profit

AIM CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AIM CONSULTING AS

Who owns AIM CONSULTING AS?

CHRISTIAN HOPE is the largest registered owner, with 100.0%.

What is the revenue of AIM CONSULTING AS?

AIM CONSULTING AS had revenue of NOK 520,000 in 2025.

Who is the general manager of AIM CONSULTING AS?

Christian Hope is registered as general manager of AIM CONSULTING AS.

Where is AIM CONSULTING AS based?

AIM CONSULTING AS has its business address in Bremnes.

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.