BIZTRAC BETA
COMPANY REGISTER PROFILE
915951686 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

PSS HOLDING AS

Org. no. 915951686 Limited company (AS) Skien Incorporated 2015 Active
Ownership graph ↗
Equity NOK 151,000
Incorporated 2015
Share capital NOK 50,000

PSS HOLDING AS is registered as a limited company in Skien, Telemark with organisation number 915951686. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte aksjer og selskapsandeler i andre selskaper, og annet som hører naturlig sammen med dette.”.

Key figures · 2025

Equity
NOK 151,000
▲ +0 %
Est. value
NOK 138,000

Financial health · 2025

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

Who owns PSS HOLDING AS?

PSS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PSS HOLDING AS own?

PSS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PSS HOLDING AS

Who owns PSS HOLDING AS?

PÅL MATHISEN is the largest registered owner, with 100.0%.

Where is PSS HOLDING AS based?

PSS HOLDING AS has its business address in Skien.

Property

Business address Nedre Åsen 19, 3731 Skien
Cadastral unit 4003-213/185/0/0
Building Enebolig · 1 unit

13 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.