BIZTRAC BETA
Other technical consultancy

ROKKE CONSULT AS

Org. no. 912698572 Limited company (AS) Stjørdal Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 39,000
Operating profit NOK −42,000
Equity NOK 1.9m
Incorporated 2013
Share capital NOK 30,000

Signals

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

ROKKE CONSULT AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 912698572. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive konsulentvirksomhet innen audioteknikk og alt som naturlig hører inn under slik virksomhet. Selskapet kan også delta i andre selskaper og investere i verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 39,000 in revenue and NOK −42,000 in operating profit.

Key figures · 2025

Revenue
NOK 39,000
Operating profit
NOK −42,000
Equity
NOK 1.9m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns ROKKE CONSULT AS?

ALF JOHNY ROKKE
ROKKE CONSULT AS
NOK 39,000 rev. · NOK −42,000 profit

ROKKE CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROKKE CONSULT AS

Who owns ROKKE CONSULT AS?

ALF JOHNY ROKKE is the largest registered owner, with 100.0%.

What is the revenue of ROKKE CONSULT AS?

ROKKE CONSULT AS had revenue of NOK 39,000 in 2025.

Who is the general manager of ROKKE CONSULT AS?

Alf Johny Rokke is registered as general manager of ROKKE CONSULT AS.

Where is ROKKE CONSULT AS based?

ROKKE CONSULT AS has its business address in Stjørdal.

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.