BIZTRAC BETA
Business and other management consultancy activities

EXECUTIVE COACHING AS

Org. no. 932306654 Limited company (AS) Kristiansand Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 28,000
Operating profit NOK −46,000
Equity NOK −23,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−23k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−46k kr).

EXECUTIVE COACHING AS is registered as a limited company in Kristiansand, Agder with organisation number 932306654. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Ledelsesrådgivning, coaching, opplæring, nettkurs, rådgivende.”. The most recent filed accounts, for the 2024 financial year, show NOK 28,000 in revenue and NOK −46,000 in operating profit.

Key figures · 2024

Revenue
NOK 28,000
Operating profit
NOK −46,000
Equity
NOK −23,000

Financial health · 2024

Liquidity
-2.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-42.9%
Weak
Equity as a share of total capital

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

Who owns EXECUTIVE COACHING AS?

TAMAS POCZE
EXECUTIVE COACHING AS
NOK 28,000 rev. · NOK −46,000 profit

EXECUTIVE COACHING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EXECUTIVE COACHING AS

Who owns EXECUTIVE COACHING AS?

TAMAS POCZE is the largest registered owner, with 100.0%.

What is the revenue of EXECUTIVE COACHING AS?

EXECUTIVE COACHING AS had revenue of NOK 28,000 in 2024.

Where is EXECUTIVE COACHING AS based?

EXECUTIVE COACHING AS has its business address in Kristiansand S.

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.