BIZTRAC BETA
COMPANY REGISTER PROFILE
924437030 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

REPE HOLDING AS

Org. no. 924437030 Limited company (AS) Stjørdal Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 100,000
Operating profit NOK −35,000
Equity NOK 312,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

REPE HOLDING AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 924437030. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Holdingselskap for aksjeselskap, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 100,000 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 100,000
Operating profit
NOK −35,000
Equity
NOK 312,000
Est. value
NOK 227,000

Financial health · 2025

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

Who owns REPE HOLDING AS?

REIDAR PETTERSEN
REPE HOLDING AS
NOK 100,000 rev. · NOK −35,000 profit

REPE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REPE HOLDING AS

Who owns REPE HOLDING AS?

REIDAR PETTERSEN is the largest registered owner, with 100.0%.

What is the revenue of REPE HOLDING AS?

REPE HOLDING AS had revenue of NOK 100,000 in 2025.

Who is the general manager of REPE HOLDING AS?

Reidar Pettersen is registered as general manager of REPE HOLDING AS.

Where is REPE HOLDING AS based?

REPE HOLDING 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.