BIZTRAC BETA
Joinery installation

PGM SERVICE AS

Org. no. 926403079 Limited company (AS) Fredrikstad Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 134,000
Equity NOK 289,000
Incorporated 2020
Share capital NOK 30,000

PGM SERVICE AS is registered as a limited company in Fredrikstad, Østfold with organisation number 926403079. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøkkenmontør. Renovasjon og vedlikehold, interiør oppussing, snekring, utendørs og innendørs maling, gulvlegging. Vask av private hus og kontor, transporttjenester som varetransport med personbil eller varebil og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 134,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 134,000
Equity
NOK 289,000
Est. value
NOK 583,000

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.9%
Good
Equity as a share of total capital

Who owns PGM SERVICE AS?

PAWEL GRZEGORZ MISKIEWICZ
PGM SERVICE AS
NOK 2.4m rev. · NOK 134,000 profit

PGM SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PGM SERVICE AS

Who owns PGM SERVICE AS?

PAWEL GRZEGORZ MISKIEWICZ is the largest registered owner, with 100.0%.

What is the revenue of PGM SERVICE AS?

PGM SERVICE AS had revenue of NOK 2.4m in 2025.

Who is the general manager of PGM SERVICE AS?

Pawel Grzegorz Miskiewicz is registered as general manager of PGM SERVICE AS.

Where is PGM SERVICE AS based?

PGM SERVICE AS has its business address in Rolvsøy.

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.