BIZTRAC BETA
Computer programming activities

POLYMINO AS

Org. no. 928584178 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −25,000
Equity NOK 426,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

POLYMINO AS is registered as a limited company in Drammen, Buskerud with organisation number 928584178. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Produktutvikling og konsulentvirksomhet hovedsakelig innenfor IKT. Skal også drive investering, herunder kjøp og salg av selskapsandeler, obligasjoner og øvrige finansielle instrumenter og formuesobjekter, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −25,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −25,000
Equity
NOK 426,000
Est. value
NOK 771,000

Financial health · 2024

Liquidity
3.86
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
74.1%
Very good
Equity as a share of total capital

Who owns POLYMINO AS?

ERIK RYBAKKEN
POLYMINO AS
NOK 0 rev. · NOK −25,000 profit

POLYMINO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POLYMINO AS

Who owns POLYMINO AS?

ERIK RYBAKKEN is the largest registered owner, with 100.0%.

What is the revenue of POLYMINO AS?

POLYMINO AS had revenue of NOK 0 in 2024.

Who is the general manager of POLYMINO AS?

Erik Rybakken is registered as general manager of POLYMINO AS.

Where is POLYMINO AS based?

POLYMINO AS has its business address in Drammen.

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.