Gambling and betting activities
What this code covers
Use this division for gambling and betting activities when the main activity includes Gambling and betting activities. Check exclusions and nearby codes before applying it to a mixed activity.
Official NACE Rev. 2.1 labels and explanatory notes are imported from the source dataset. Plain-language explanations are shown separately so readers can compare interpretation with the source text.
- This division includes the operation of gambling facilities (for example, casinos, bingo halls, electronic gambling machines) and the provision of gambling services (for example, lotteries, off-track betting). These gambling and betting activities can be carried out in gambling facilities or online.
- operation of coin-operated games, see 93.29
- Compare with 93.29, 90, 91 when the main activity overlaps another code.
- Check national equivalent caveats before using this code for local registration or filing workflows.
- If the main revenue activity appears in an exclusion, compare the alternative code before deciding.
Use this guide as classification support, not legal, tax, filing, or regulatory advice.
- - This division includes the operation of gambling facilities (for example, casinos, bingo halls, electronic gambling machines) and the provision of gambling services (for example, lotteries, off-track betting). These gambling and betting activities can be carried out in gambling facilities or online.
- - operation of coin-operated games, see 93.29
- - Gambling and betting activities
- - Operation of coin-operated games
What is NACE 92 used for?
Use NACE 92 for gambling and betting activities when the main activity matches this scope: Use this division for gambling and betting activities when the main activity includes Gambling and betting activities. Check exclusions and nearby codes before applying it to a mixed activity.
What are typical examples for 92?
Typical examples include Gambling and betting activities.
When might 92 not be the right code?
Review another code when the activity is closer to operation of coin-operated games, see 93.29.
Which codes should I compare before choosing 92?
Compare 92 with 93.29 Amusement and recreation activities n.e.c., 90 Arts creation and performing arts activities, and 91 Libraries, archives, museums and other cultural activities when the activity description is ambiguous.
Use this class for amusement and recreation activities n.e.c. when the main activity includes Operation (exploitation) of coin-operated games and Rental of leisure and pleasure equipment as an integral part of recreational facilities. Check exclusions and nearby codes before applying it to a mixed activity.
Use this division for arts creation and performing arts activities when the main activity includes Arts creation activities and Activities of performing arts. Check exclusions and nearby codes before applying it to a mixed activity.
Use this division for libraries, archives, museums and other cultural activities when the main activity includes It also includes the preservation and exhibition of objects, sites and natural wonders of historical, cultural or educational interest (for example, World Heritage Sites).. Check exclusions and nearby codes before applying it to a mixed activity.
Use this division for sports activities and amusement and recreation activities when the main activity includes Organisation of sporting events. Check exclusions and nearby codes before applying it to a mixed activity.
Use this group for the broader activity area of gambling and betting activities, including Gambling and betting activities. Open the child codes when a more specific code is needed.
Use this section for aRTS, SPORTS AND RECREATION when the main activity includes Arts creation and performing arts activities and Libraries, archives, museums and other cultural activities. Check exclusions and nearby codes before applying it to a mixed activity.
Rev. 2 code 92 maps to the same Rev. 2.1 class 92 Gambling and betting activities.
Official close match imported from NACE Rev. 2.1.
Low operational impact is expected, but systems should still store the target Rev. 2.1 version explicitly.
Confirm the target version field and update references where Rev. 2.1 is required.