BIZTRAC BETA
Non-specialised wholesale trade

POKAL1 AS

Org. no. 914144833 Limited company (AS) Moss Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 391,000
Operating profit NOK −60,000
Equity NOK 256,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−60k kr).

POKAL1 AS is registered as a limited company in Moss, Østfold with organisation number 914144833. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av premier og promotionartikler og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 391,000 in revenue and NOK −60,000 in operating profit.

Key figures · 2024

Revenue
NOK 391,000
Operating profit
NOK −60,000
Equity
NOK 256,000
Est. value
NOK 235,000

Financial health · 2024

Liquidity
-8.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.1%
Very good
Equity as a share of total capital

Who owns POKAL1 AS?

SVEIN LINDBLOM
POKAL1 AS
NOK 391,000 rev. · NOK −60,000 profit

POKAL1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POKAL1 AS

Who owns POKAL1 AS?

SVEIN LINDBLOM is the largest registered owner, with 100.0%.

What is the revenue of POKAL1 AS?

POKAL1 AS had revenue of NOK 391,000 in 2024.

Who is the general manager of POKAL1 AS?

Svein Lindblom is registered as general manager of POKAL1 AS.

Where is POKAL1 AS based?

POKAL1 AS has its business address in Moss.

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.