BIZTRAC BETA
Retail sale of clothing

PAA HJØRNET AS

Org. no. 988463000 Limited company (AS) Kragerø Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK 517,000
Equity NOK 628,000
Incorporated 2005
Employees 11
Share capital NOK 100,000

Signals

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

PAA HJØRNET AS is registered as a limited company in Kragerø, Telemark with organisation number 988463000. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2005 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kles- og gavebutikk samt det som er naturlig beslektet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK 517,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK 517,000
Equity
NOK 628,000
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns PAA HJØRNET AS?

SOT INVEST AS
PAA HJØRNET AS
NOK 5.2m rev. · NOK 517,000 profit

PAA HJØRNET AS has 1 registered shareholder:

All shareholders and roles →

Group structure

PAA HJØRNET AS er morselskap for 5 datterselskaper:

Frequently asked questions about PAA HJØRNET AS

Who owns PAA HJØRNET AS?

SOT INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of PAA HJØRNET AS?

PAA HJØRNET AS had revenue of NOK 5.2m in 2024.

Who is the general manager of PAA HJØRNET AS?

Wenche Mastereid is registered as general manager of PAA HJØRNET AS.

Where is PAA HJØRNET AS based?

PAA HJØRNET AS has its business address in Kragerø.

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.