biztrac. BETA
COMPANY REGISTER PROFILE
928855368 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

HAREHOPP AS

Org. no. 928855368 Limited company (AS) Oslo Incorporated 2021 Active
Revenue 2025 NOK 26,000
Operating profit NOK −777,000
Equity NOK −1.1m
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).

HAREHOPP AS is registered as a limited company in Oslo, Oslo with organisation number 928855368. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Event/arrangementer. Guiding. Utleie av motorkjøretøy.”. The most recent filed accounts, for the 2025 financial year, show NOK 26,000 in revenue and NOK −777,000 in operating profit.

Former names: ROGDE INVEST AS

Key figures · 2025

Revenue
NOK 26,000
Operating profit
NOK −777,000
▼ −106 %
Equity
NOK −1.1m
▼ −206 %

Financial health · 2025

Liquidity
27.96
Very good
Current assets ÷ current liabilities
Profitability
-58.1%
Not satisfactory
Return on total assets
Solidity
-78.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HAREHOPP AS?

HAREHOPP AS
NOK 26,000 rev. · NOK −777,000 profit

HAREHOPP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAREHOPP AS

Who owns HAREHOPP AS?

ROGDE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HAREHOPP AS?

HAREHOPP AS had revenue of NOK 26,000 in 2025.

Who is the general manager of HAREHOPP AS?

Vigleik Rogde is registered as general manager of HAREHOPP AS.

Where is HAREHOPP AS based?

HAREHOPP 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 03.10.2026.

Report a problem

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