BIZTRAC BETA
Accounting and bookkeeping

POLKON REGNSKAP AS

Org. no. 928115690 Limited company (AS) Drammen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 944,000
Operating profit NOK 11,000
Equity NOK 42,000
Incorporated 2021
Share capital NOK 30,000

POLKON REGNSKAP AS is registered as a limited company in Drammen, Buskerud with organisation number 928115690. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Salg tjenester innenfor regnskapstjenester og alt hva dermed står i forbindelse, herunder deltakelse i andre selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 944,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2024

Revenue
NOK 944,000
Operating profit
NOK 11,000
Equity
NOK 42,000
Est. value
NOK 78,000

Financial health · 2024

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.9%
Weak
Equity as a share of total capital

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

Who owns POLKON REGNSKAP AS?

IZABELA GOLIMOWSKA
POLKON REGNSKAP AS
NOK 944,000 rev. · NOK 11,000 profit

POLKON REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POLKON REGNSKAP AS

Who owns POLKON REGNSKAP AS?

IZABELA GOLIMOWSKA is the largest registered owner, with 100.0%.

What is the revenue of POLKON REGNSKAP AS?

POLKON REGNSKAP AS had revenue of NOK 944,000 in 2024.

Who is the general manager of POLKON REGNSKAP AS?

Izabela Golimowska is registered as general manager of POLKON REGNSKAP AS.

Where is POLKON REGNSKAP AS based?

POLKON REGNSKAP AS has its business address in Krokstadelva.

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.