BIZTRAC BETA
COMPANY REGISTER PROFILE
988977799 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

BEPE HOLDING AS

Org. no. 988977799 Limited company (AS) Meråker Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 2.8m
Incorporated 2005
Share capital NOK 150,000

Signals

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

BEPE HOLDING AS is registered as a limited company in Meråker, Trøndelag with organisation number 988977799. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Investere og eie aksjer i andre selskaper, kjøp og salg av fast eiendom samt drive rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
▲ +13 %
Equity
NOK 2.8m
▲ +8 %
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
7.6%
Satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns BEPE HOLDING AS?

BEPE HOLDING AS
NOK 0 rev. · NOK −18,000 profit

BEPE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BEPE HOLDING AS own?

BEPE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BEPE HOLDING AS

Who owns BEPE HOLDING AS?

BJØRN EGIL PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of BEPE HOLDING AS?

BEPE HOLDING AS had revenue of NOK 0 in 2025.

Where is BEPE HOLDING AS based?

BEPE HOLDING AS has its business address in Meråker.

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.