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

PER HINDAHL AS

Org. no. 968742752 Limited company (AS) Oslo Incorporated 1993 Active
Revenue 2025 NOK 9.4m
Operating profit NOK 316,000
Equity NOK 3.0m
Incorporated 1993
Employees 23
Share capital NOK 100,000

PER HINDAHL AS is registered as a limited company in Oslo, Oslo with organisation number 968742752. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 1993 and has 23 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kafe- og restaurantdrift, utleie av minigolf, drift av campingplass og hva dermed står i for- bindelse, samt å interessere seg i andre foretag- ender.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK 316,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.4m
▲ +5 %
Operating profit
NOK 316,000
▼ −43 %
Equity
NOK 3.0m
▲ +10 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
4.04
Very good
Current assets ÷ current liabilities
Profitability
9.5%
Satisfactory
Return on total assets
Solidity
76.9%
Very good
Equity as a share of total capital

Who owns PER HINDAHL AS?

PER HINDAHL AS
NOK 9.4m rev. · NOK 316,000 profit

PER HINDAHL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PER HINDAHL AS

Who owns PER HINDAHL AS?

Per Otto Hindahl is the largest registered owner, with 100.0%.

What is the revenue of PER HINDAHL AS?

PER HINDAHL AS had revenue of NOK 9.4m in 2025.

Who is the general manager of PER HINDAHL AS?

Per Otto Hindahl is registered as general manager of PER HINDAHL AS.

Where is PER HINDAHL AS based?

PER HINDAHL 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 03.10.2026.

Report a problem

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