BIZTRAC BETA
Manufacture of bread; manufacture of fresh pastry goods and cakes

PANAME SHOP AS

Org. no. 930343064 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 15.3m
Operating profit NOK 870,000
Equity NOK −263,000
Incorporated 2022
Employees 15
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−263k kr).

PANAME SHOP AS is registered as a limited company in Oslo, Oslo with organisation number 930343064. The business is classified under manufacture of bread; manufacture of fresh pastry goods and cakes (NACE 10.710). The company was incorporated in 2022 and has 15 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Produksjon og salg av næringsmidler, herunder bakeri, konditori, kaffe og sjokolade produkter, og det som hører naturlig til under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.3m in revenue and NOK 870,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.3m
Operating profit
NOK 870,000
Equity
NOK −263,000
Est. value
NOK 7.2m

Financial health · 2024

Liquidity
0.64
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-8.2%
Weak
Equity as a share of total capital

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

Who owns PANAME SHOP AS?

PANAME GRUPPEN AS
PANAME SHOP AS
NOK 15.3m rev. · NOK 870,000 profit

PANAME SHOP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PANAME SHOP AS

Who owns PANAME SHOP AS?

PANAME GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of PANAME SHOP AS?

PANAME SHOP AS had revenue of NOK 15.3m in 2024.

Where is PANAME SHOP AS based?

PANAME SHOP 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 15.06.2026.

Report a problem

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