BIZTRAC BETA
COMPANY REGISTER PROFILE
959179468 ORG. NO. 8 SECTIONS
Active UPDATED 02.09.2026
Contract catering service activities and other food service activities

VY BUSS BEDRIFTSIDRETTSLAG TRØNDELAG

Org. no. 959179468 Association/club/organisation (FLI) Trondheim Incorporated 1922 Active
Ownership graph ↗
Incorporated 1922

Signals

1 flags
  • Nylig endring 2026-08-18 Adresseendring registrert 2026-08-18.

VY BUSS BEDRIFTSIDRETTSLAG TRØNDELAG is registered as a association/club/organisation in Trondheim, Trøndelag with organisation number 959179468. The business is classified under contract catering service activities and other food service activities (NACE 56.220). The company was incorporated in 1922. The company's stated purpose is: “Å bidra til idrett og friluftsliv som et ledd i den fysiske fostring blant sjåfører og kontoransatte ved Nettbuss Trøndelag. Vi har åtte aktive bowlinglag, to fotballag og et skytterlag.”.

Former names: TRONDHEIM TRAFIKKSELSKAP BEDRIFTSIDRETTSLAG KANTINER, NETTBUSS TRØNDELAGS BEDRIFTSIDRETTSLAG

Who owns VY BUSS BEDRIFTSIDRETTSLAG TRØNDELAG?

No shareholders are registered for VY BUSS BEDRIFTSIDRETTSLAG TRØNDELAG in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about VY BUSS BEDRIFTSIDRETTSLAG TRØNDELAG

Where is VY BUSS BEDRIFTSIDRETTSLAG TRØNDELAG based?

VY BUSS BEDRIFTSIDRETTSLAG TRØNDELAG has its business address in Tiller.

Property

Business address Østre Rosten 125, 7093 Tiller
Cadastral unit 5001-313/632/0/0
Building Annen kontorbygning · 1 unit

4 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.