biztrac. BETA
COMPANY REGISTER PROFILE
915129862 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Event catering activities

PAKORA AS

Org. no. 915129862 Limited company (AS) Vardø Incorporated 2015 Active
Revenue 2025 NOK 1.8m
Operating profit NOK −42,000
Equity NOK −84,000
Incorporated 2015
Employees 10
Share capital NOK 30,000

Signals

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

PAKORA AS is registered as a limited company in Vardø, Finnmark with organisation number 915129862. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2015 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive cateringvirksomhet, samt restaurantvirksomhet med salg av mat.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −42,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▲ +1 %
Operating profit
NOK −42,000
▼ −242 %
Equity
NOK −84,000
▼ −105 %
Est. value
NOK 71,000

Financial health · 2025

Liquidity
0.63
Weak
Current assets ÷ current liabilities
Profitability
-13.4%
Not satisfactory
Return on total assets
Solidity
-46.9%
Weak
Equity as a share of total capital

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

Who owns PAKORA AS?

PAKORA AS
NOK 1.8m rev. · NOK −42,000 profit

PAKORA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PAKORA AS

Who owns PAKORA AS?

Naruemol Pholkor is the largest registered owner, with 100.0%.

What is the revenue of PAKORA AS?

PAKORA AS had revenue of NOK 1.8m in 2025.

Who is the general manager of PAKORA AS?

Naruemol Pholkor is registered as general manager of PAKORA AS.

Where is PAKORA AS based?

PAKORA AS has its business address in Vardø.

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.