BIZTRAC BETA
Publishing of books

HOGREFE NORGE AS

Org. no. 932802422 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 11.5m
Operating profit NOK 2.3m
Equity NOK 1.6m
Incorporated 2023
Employees 8
Share capital NOK 30,000

HOGREFE NORGE AS is registered as a limited company in Oslo, Oslo with organisation number 932802422. The business is classified under publishing of books (NACE 58.110). The company was incorporated in 2023 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling og publisering av bøker, tester, tidsskrifter og programvare med fokus på psykologi og relaterte felt og tilsvarende tjenester som rådgivning og vurderinger, opplæring, seminarer og andre som oppfyller dette formålet.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.5m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 11.5m
Operating profit
NOK 2.3m
Equity
NOK 1.6m
Est. value
NOK 13.4m

Financial health · 2024

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.8%
Satisfactory
Equity as a share of total capital

Who owns HOGREFE NORGE AS?

HOGREFE VERLAGSGRUPPE GMBH
HOGREFE NORGE AS
NOK 11.5m rev. · NOK 2.3m profit

HOGREFE NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOGREFE NORGE AS

Who owns HOGREFE NORGE AS?

HOGREFE VERLAGSGRUPPE GMBH is the largest registered owner, with 100.0%.

What is the revenue of HOGREFE NORGE AS?

HOGREFE NORGE AS had revenue of NOK 11.5m in 2024.

Who is the general manager of HOGREFE NORGE AS?

Vibeke Jensen Sending is registered as general manager of HOGREFE NORGE AS.

Where is HOGREFE NORGE AS based?

HOGREFE NORGE AS has its business address in Oslo.

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.