BIZTRAC BETA
COMPANY REGISTER PROFILE
962563015 ORG. NO. 2024 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Business and other management consultancy activities

JOHRE RÅDGIVNING

Org. no. 962563015 Sole proprietorship (ENK) Skien Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 2.9m
Equity NOK 888,000

Signals

1 flags
  • Nylig endring 2026-08-19 Adresseendring registrert 2026-08-19.

JOHRE RÅDGIVNING is registered as a sole proprietorship in Skien, Telemark with organisation number 962563015. The business is classified under business and other management consultancy activities (NACE 70.200). The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 2.9m in operating profit.

Former names: JOHRE REVISJON

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 2.9m
Equity
NOK 888,000
Est. value
NOK 9.9m

Financial health · 2024

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

Who owns JOHRE RÅDGIVNING?

No shareholders are registered for JOHRE RÅDGIVNING in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about JOHRE RÅDGIVNING

What is the revenue of JOHRE RÅDGIVNING?

JOHRE RÅDGIVNING had revenue of NOK 5.3m in 2024.

Where is JOHRE RÅDGIVNING based?

JOHRE RÅDGIVNING has its business address in Skien.

Property

Business address Fartangen 9, 3725 Skien
Cadastral unit 4003-300/4898/0/0
Building Tomannsbolig, vertikal · 2 units

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.