biztrac. BETA
COMPANY REGISTER PROFILE
935004306 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

PIR 1 AS

Org. no. 935004306 Limited company (AS) Risør Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 600,000
Operating profit NOK 162,000
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

PIR 1 AS is registered as a limited company in Risør, Agder with organisation number 935004306. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie av, drift av restauranter, barer, nattklubber og annen serveringsvirksomhet samt beslektet virksomhet, herunder eie av andeler i selskaper med tilsvarende formål og eie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 600,000 in revenue and NOK 162,000 in operating profit.

Key figures · 2025

Revenue
NOK 600,000
Operating profit
NOK 162,000
Equity
NOK 30,000
Est. value
NOK 372,000

Financial health · 2025

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

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

Who owns PIR 1 AS?

PIR 1 AS
NOK 600,000 rev. · NOK 162,000 profit

PIR 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PIR 1 AS

Who owns PIR 1 AS?

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

What is the revenue of PIR 1 AS?

PIR 1 AS had revenue of NOK 600,000 in 2025.

Where is PIR 1 AS based?

PIR 1 AS has its business address in Risør.

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

Report a problem

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