Kontakto

Santala Print Oy

Aktiivinen
Business ID 0678228-5
|
VAT-number FI06782285

Santala Print Oy (0678228-5)

Louhekuja 4

62100 LAPUA

Description

Santala Print Oy (0678228-5) is a limited company founded in 1987, located in Lapua. Its main industry is Muu painaminen.

Info

Official name:

Santala Print Oy

Company form:

Osakeyhtiö

Year of foundation:

1987

Domicile city:

Lapua

Official language:

Suomi

Industry:

Muu painaminen

Official address:

Louhekuja 4, 62100 LAPUA

VAT ID:

FI06782285

Source: PRH & YTJ

Information updates automatically
Kontakto Oy does not charge companies for being listed or for updating their information. If you have any questions, please contact support@kontakto.fi.

Website

Technologies were detected automatically from the site.

Kotisivukamu

Is Santala Print Oy your company? Kotisivukamu can build a new site from your current content in about half an hour.

Renew the site with Kotisivukamu →

E-invoicing addresses

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

Active registrations

6 in force
  • Arvonlisäverorekisteri Verohallinto Registered: 9.7.2019 In force
  • Arvonlisäverorekisteri Verohallinto Registered: 9.7.2019 In force
  • Ennakkoperintärekisteri Verohallinto Registered: 25.3.2017 In force
  • Kaupparekisteri PRH Registered: 27.1.1988 In force
  • Työnantajarekisteri Verohallinto Registered: 30.3.2001 In force
  • Verohallinnon perustiedot Verohallinto Registered: 1.6.2026 In force

Source: PRH & Finnish Tax Administration (YTJ)

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.