BIZTRAC BETA
Retail sale of clothing

PROKLÆR AS

Org. no. 925567027 Limited company (AS) Hamarøy Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 10.9m
Operating profit NOK −1.3m
Equity NOK −5.1m
Incorporated 2020
Employees 9
Share capital NOK 300,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−5,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,3 mill kr).

PROKLÆR AS is registered as a limited company in Hamarøy, Nordland with organisation number 925567027. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2020 and has 9 registered employees. Registered share capital is NOK 300,000, divided into 100 shares. The company's stated purpose is: “Butikkhandel med arbeidsklær og verneutstyr, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.9m in revenue and NOK −1.3m in operating profit.

Key figures · 2024

Revenue
NOK 10.9m
Operating profit
NOK −1.3m
Equity
NOK −5.1m

Financial health · 2024

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

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

Who owns PROKLÆR AS?

UAB REWELLY
PROKLÆR AS
NOK 10.9m rev. · NOK −1.3m profit

PROKLÆR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROKLÆR AS

Who owns PROKLÆR AS?

UAB REWELLY is the largest registered owner, with 50.0%.

What is the revenue of PROKLÆR AS?

PROKLÆR AS had revenue of NOK 10.9m in 2024.

Who is the general manager of PROKLÆR AS?

Gediminas Paulauskas is registered as general manager of PROKLÆR AS.

Where is PROKLÆR AS based?

PROKLÆR AS has its business address in Storjorda I Tysfjorden.

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.