BIZTRAC BETA
Other education activities

INTERACTION CONSULTING AS

Org. no. 976180666 Limited company (AS) Nesodden Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 321,000
Operating profit NOK −511,000
Equity NOK 921,000
Incorporated 1996
Share capital NOK 100,000

Signals

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

INTERACTION CONSULTING AS is registered as a limited company in Nesodden, Akershus with organisation number 976180666. The business is classified under other education activities (NACE 85.597). The company was incorporated in 1996. Registered share capital is NOK 100,000. The company's stated purpose is: “Lederutvikling”. The most recent filed accounts, for the 2024 financial year, show NOK 321,000 in revenue and NOK −511,000 in operating profit.

Key figures · 2024

Revenue
NOK 321,000
Operating profit
NOK −511,000
Equity
NOK 921,000
Est. value
NOK 745,000

Financial health · 2024

Liquidity
7.69
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.0%
Very good
Equity as a share of total capital

Who owns INTERACTION CONSULTING AS?

PEDER CHRISTOFFER WROLDSEN
INTERACTION CONSULTING AS
NOK 321,000 rev. · NOK −511,000 profit

INTERACTION CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INTERACTION CONSULTING AS

Who owns INTERACTION CONSULTING AS?

PEDER CHRISTOFFER WROLDSEN is the largest registered owner, with 100.0%.

What is the revenue of INTERACTION CONSULTING AS?

INTERACTION CONSULTING AS had revenue of NOK 321,000 in 2024.

Who is the general manager of INTERACTION CONSULTING AS?

Peder Christoffer Wroldsen is registered as general manager of INTERACTION CONSULTING AS.

Where is INTERACTION CONSULTING AS based?

INTERACTION CONSULTING AS has its business address in Nesodden.

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.