Kontakto

Juhkon Oy

Aktiivinen
Business ID 2939778-5
|
VAT-number FI29397785

Juhkon Oy (2939778-5)

Puhuri 11 B 12

20900 TURKU

Contact details

Phone number not declared.

Puhuri 11 B 12 20900 TURKU

juha.konkka@gmail.com

No website on record.

Description

Juhkon Oy (2939778-5) is a limited company founded in 2018, located in Turku. Its main industry is Muu muualla luokittelematon monenlainen erikoistunut rakennustoiminta.

Info

Official name:

Juhkon Oy

Company form:

Osakeyhtiö

Year of foundation:

2018

Domicile city:

Turku

Official language:

Suomi

Industry:

Muu muualla luokittelematon monenlainen erikoistunut rakennustoiminta

Official address:

Puhuri 11 B 12, 20900 TURKU

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 5.10.2018
Ennakkoperintärekisteri 5.10.2018
Kaupparekisteri 3.10.2018
Kaupparekisteri 17.9.2018
Työnantajarekisteri 5.10.2018
Verohallinnon perustiedot 5.8.2025

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.