BIZTRAC BETA
Activities of call centres

MAX DIALOG AS

Org. no. 999607454 Limited company (AS) Kvæfjord Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 8.3m
Operating profit NOK 813,000
Equity NOK 2.8m
Incorporated 2013
Share capital NOK 30,000

MAX DIALOG AS is registered as a limited company in Kvæfjord, Troms with organisation number 999607454. The business is classified under activities of call centres (NACE 82.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Telemarketing, telefonsalg og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.3m in revenue and NOK 813,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.3m
Operating profit
NOK 813,000
Equity
NOK 2.8m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns MAX DIALOG AS?

KIM ARE RØCH HÅKENSTAD
MAX DIALOG AS
NOK 8.3m rev. · NOK 813,000 profit

MAX DIALOG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAX DIALOG AS

Who owns MAX DIALOG AS?

KIM ARE RØCH HÅKENSTAD is the largest registered owner, with 100.0%.

What is the revenue of MAX DIALOG AS?

MAX DIALOG AS had revenue of NOK 8.3m in 2024.

Who is the general manager of MAX DIALOG AS?

Kim Are Røch Håkenstad is registered as general manager of MAX DIALOG AS.

Where is MAX DIALOG AS based?

MAX DIALOG AS has its business address in Borkenes.

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.