BIZTRAC BETA
Restaurant activities

PAPA'S TAKEAWAY AS

Org. no. 996201708 Limited company (AS) Askøy Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 980,000
Operating profit NOK −497,000
Equity NOK 139,000
Incorporated 2010
Employees 13
Share capital NOK 250,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−497k kr).
  • Nylig endring 2026-05-04 Adresseendring registrert 2026-05-04.

PAPA'S TAKEAWAY AS is registered as a limited company in Askøy, Vestland with organisation number 996201708. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2010 and has 13 registered employees. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Drift av gatekjøkken.”. The most recent filed accounts, for the 2024 financial year, show NOK 980,000 in revenue and NOK −497,000 in operating profit.

Key figures · 2024

Revenue
NOK 980,000
Operating profit
NOK −497,000
Equity
NOK 139,000
Est. value
NOK 753,000

Financial health · 2024

Liquidity
0.97
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.3%
Satisfactory
Equity as a share of total capital

Who owns PAPA'S TAKEAWAY AS?

KELSAR INVEST AS
PAPA'S TAKEAWAY AS
NOK 980,000 rev. · NOK −497,000 profit

PAPA'S TAKEAWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PAPA'S TAKEAWAY AS

Who owns PAPA'S TAKEAWAY AS?

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

What is the revenue of PAPA'S TAKEAWAY AS?

PAPA'S TAKEAWAY AS had revenue of NOK 980,000 in 2024.

Who is the general manager of PAPA'S TAKEAWAY AS?

Egil Leganger is registered as general manager of PAPA'S TAKEAWAY AS.

Where is PAPA'S TAKEAWAY AS based?

PAPA'S TAKEAWAY AS has its business address in Hauglandshella.

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.