BIZTRAC BETA
Architectural activities

PONS HOLDING AS

Org. no. 933555771 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1,000
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

PONS HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 933555771. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 1,000 in revenue.

Key figures · 2024

Revenue
NOK 1,000
Equity
NOK 30,000
Est. value
NOK 16,000

Financial health · 2024

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

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

Who owns PONS HOLDING AS?

BJARNE ASP
PONS HOLDING AS
NOK 1,000 rev.

PONS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PONS HOLDING AS own?

PONS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PONS HOLDING AS

Who owns PONS HOLDING AS?

BJARNE ASP is the largest registered owner, with 100.0%.

What is the revenue of PONS HOLDING AS?

PONS HOLDING AS had revenue of NOK 1,000 in 2024.

Who is the general manager of PONS HOLDING AS?

Bjarne Asp is registered as general manager of PONS HOLDING AS.

Where is PONS HOLDING AS based?

PONS HOLDING 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 15.06.2026.

Report a problem

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