Kontakto

Rompun kone ja Metsäpalvelu Oy

Aktiivinen
Business ID 1564402-8
|
VAT-number FI15644028

Rompun kone ja Metsäpalvelu Oy (1564402-8)

c/o Välimäki

Punkalaitumentie 1080

38280 SASTAMALA

Contact details

Phone number not declared.

Visiting address not declared.

Email not declared.

No website on record.

Description

Rompun kone ja Metsäpalvelu Oy (1564402-8) is a limited company founded in 1999, located in Sastamala. Its main industry is Puunkorjuu.

Info

Official name:

Rompun kone ja Metsäpalvelu Oy

Company form:

Osakeyhtiö

Year of foundation:

1999

Domicile city:

Sastamala

Official language:

Suomi

Industry:

Puunkorjuu

Official address:

c/o Välimäki, Punkalaitumentie 1080, 38280 SASTAMALA

Source: PRH & YTJ

Information updates automatically
Kontakto Oy never calls anyone and never asks for money to correct or update information. We also never send unexpected invoices. If someone contacts you or you receive an invoice in our name, it is a scam. You can contact us at support@kontakto.fi, but we will never reach out to ask for anything.
UUTTA
Kotisivukamu

Does your business need a website?

Kontakto's new Kotisivukamu service builds your business a professional website in 30 minutes - no technical skills needed.

Try for free →

E-invoicing addresses

E-invoicing addresses are only available for registered users. Sign-up is free of charge.

Registers

Arvonlisäverorekisteri 31.3.2001
Ennakkoperintärekisteri 25.2.2017
Kaupparekisteri 17.1.2000
Työnantajarekisteri 31.3.2001
Verohallinnon perustiedot 5.3.2026

Interface usage

Would you like this data directly in your billing system?

By integrating Kontakto, you get up-to-date company information lightning fast to your own system.

Using the interface is fast and easy. Subscribe now and start integrating!

READ MORE

Info & Feedback

Data source

PRH & YTJ

Company information is collected from public registers and updated regularly. Data may be subject to delays.

Read more on our FAQ page

Spotted an error?

Let us know if any information seems incorrect. We will look into it.