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

IKIGAI CONSULTING AS

Org. no. 925093467 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 995,000
Operating profit NOK −3,000
Equity NOK 35,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

IKIGAI CONSULTING AS is registered as a limited company in Oslo, Oslo with organisation number 925093467. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Undervisning, rådgivning og konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 995,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 995,000
Operating profit
NOK −3,000
Equity
NOK 35,000
Est. value
NOK 1.1m

Financial health · 2025

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

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

Who owns IKIGAI CONSULTING AS?

ESPEN ERFJELL
IKIGAI CONSULTING AS
NOK 995,000 rev. · NOK −3,000 profit

IKIGAI CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IKIGAI CONSULTING AS

Who owns IKIGAI CONSULTING AS?

ESPEN ERFJELL is the largest registered owner, with 100.0%.

What is the revenue of IKIGAI CONSULTING AS?

IKIGAI CONSULTING AS had revenue of NOK 995,000 in 2025.

Where is IKIGAI CONSULTING AS based?

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