BIZTRAC BETA
COMPANY REGISTER PROFILE
989033050 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 25.08.2026
PEBA HOLDING AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Other real estate activities on a fee or contract basis

PEBA HOLDING AS

Org. no. 989033050 Limited company (AS) Stjørdal Incorporated 2005 In liquidation
Ownership graph ↗
Operating profit NOK −136,000
Equity NOK 1,000
Incorporated 2005
Share capital NOK 50,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−136k kr).

PEBA HOLDING AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 989033050. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2005. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter å forestå investeringsvirksomhet, eiendomsforvaltning og annen virksomhet beslektet med denne inklusive konsulentvirksomhet.”.

Key figures · 2025

Operating profit
NOK −136,000
Equity
NOK 1,000

Financial health · 2025

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

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

Who owns PEBA HOLDING AS?

SILJE BALSTAD ENGAN
PEBA HOLDING AS
· NOK −136,000 profit

PEBA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PEBA HOLDING AS

Who owns PEBA HOLDING AS?

SILJE BALSTAD ENGAN is the largest registered owner, with 100.0%.

Where is PEBA HOLDING AS based?

PEBA HOLDING AS has its business address in Hegra.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

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