BIZTRAC BETA
Retail sale of clothing

PER J GUNDERSEN AS

Org. no. 935268974 Limited company (AS) Ringerike Incorporated 1984 Active
Ownership graph ↗
Revenue 2024 NOK 22.5m
Operating profit NOK 2.0m
Equity NOK 3.2m
Incorporated 1984
Employees 14
Share capital NOK 1.5m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PER J GUNDERSEN AS is registered as a limited company in Ringerike, Buskerud with organisation number 935268974. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 1984 and has 14 registered employees. Registered share capital is NOK 1.5m, divided into 300 shares. The company's stated purpose is: “Handel med klær og skotøy og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.5m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 22.5m
Operating profit
NOK 2.0m
Equity
NOK 3.2m
Est. value
NOK 8.4m

Financial health · 2024

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

Who owns PER J GUNDERSEN AS?

TBG HOLDING AS
PER J GUNDERSEN AS
NOK 22.5m rev. · NOK 2.0m profit

PER J GUNDERSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PER J GUNDERSEN AS own?

PER J GUNDERSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PER J GUNDERSEN AS

Who owns PER J GUNDERSEN AS?

TBG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of PER J GUNDERSEN AS?

PER J GUNDERSEN AS had revenue of NOK 22.5m in 2024.

Where is PER J GUNDERSEN AS based?

PER J GUNDERSEN AS has its business address in Hønefoss.

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.