biztrac. BETA
COMPANY REGISTER PROFILE
921759010 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of sports equipment

HOFRE HOLDING AS

Org. no. 921759010 Limited company (AS) Andøy Incorporated 2018 Active
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 4,000
Incorporated 2018
Share capital NOK 40,000

Signals

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

HOFRE HOLDING AS is registered as a limited company in Andøy, Nordland with organisation number 921759010. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2018. Registered share capital is NOK 40,000, divided into 1000 shares. The company's stated purpose is: “Å eie aksjer i ett eller flere selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
▲ +11 %
Equity
NOK 4,000
▼ −54 %
Est. value
NOK 5,000

Financial health · 2025

Liquidity
0.35
Not satisfactory
Current assets ÷ current liabilities
Profitability
-17.7%
Not satisfactory
Return on total assets
Solidity
15.2%
Weak
Equity as a share of total capital

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

Who owns HOFRE HOLDING AS?

HOFRE HOLDING AS
NOK 0 rev. · NOK −5,000 profit

HOFRE HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HOFRE HOLDING AS own?

HOFRE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HOFRE HOLDING AS

Who owns HOFRE HOLDING AS?

Rodrigo Matias Fretin is the largest registered owner, with 50.0%.

What is the revenue of HOFRE HOLDING AS?

HOFRE HOLDING AS had revenue of NOK 0 in 2025.

Where is HOFRE HOLDING AS based?

HOFRE HOLDING AS has its business address in Bleik.

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.