BIZTRAC BETA
COMPANY REGISTER PROFILE
933269922 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

ÆIK AS

Org. no. 933269922 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 272,000
Operating profit NOK 3,000
Equity NOK 8,000
Incorporated 2024
Share capital NOK 30,000

ÆIK AS is registered as a limited company in Oslo, Oslo with organisation number 933269922. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Hjelpe andre individer eller selskap i å utvikle deres idéer og prosjekter gjennom prosjektutvikling og kommunikasjonsarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 272,000 in revenue and NOK 3,000 in operating profit.

Former names: CARVALHO CONSULTING AS

Key figures · 2025

Revenue
NOK 272,000
Operating profit
NOK 3,000
Equity
NOK 8,000
Est. value
NOK 18,000

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.1%
Weak
Equity as a share of total capital

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

Who owns ÆIK AS?

SYLVIO OTERHALS CARVALHO
ÆIK AS
NOK 272,000 rev. · NOK 3,000 profit

ÆIK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ÆIK AS

Who owns ÆIK AS?

SYLVIO OTERHALS CARVALHO is the largest registered owner, with 50.0%.

What is the revenue of ÆIK AS?

ÆIK AS had revenue of NOK 272,000 in 2025.

Who is the general manager of ÆIK AS?

Andrea Oterhals Carvalho is registered as general manager of ÆIK AS.

Where is ÆIK AS based?

ÆIK 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.