Kontakto

Nimlas Finland Oy

Aktiivinen
Business ID 2824749-4
|
VAT-number FI28247494

Nimlas Finland Oy (2824749-4)

Piispantilankuja 2 A

02240 ESPOO

Contact details

Phone number not declared.

Visiting address not declared.

Email not declared.

No website on record.

Description

Nimlas Finland Oy (2824749-4) is a limited company founded in 2017, located in Helsinki. Its main industry is Liikkeenjohdon konsultointi.

Info

Official name:

Nimlas Finland Oy

Company form:

Osakeyhtiö

Year of foundation:

2017

Domicile city:

Helsinki

Official language:

Suomi

Industry:

Liikkeenjohdon konsultointi

Official address:

Piispantilankuja 2 A, 02240 ESPOO

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 26.6.2019
Arvonlisäverorekisteri 26.6.2019
Ennakkoperintärekisteri 3.5.2017
Kaupparekisteri 3.4.2017
Kaupparekisteri 27.3.2017
Työnantajarekisteri 2.12.2025
Verohallinnon perustiedot 2.12.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.