StickAtlasGlobal field hockeyStickAtlas
NewsMatchesCompetitionsCountries
Club finder
NetherlandsGermanyBelgiumSpainEnglandArgentina

Explore

Club finderNewsMatchesCompetitionsCountriesNetherlandsGermanyBelgiumSpainEnglandArgentina

Contribute

Share photosShare newsReport bugsCareersDonate to development

Social

Instagram

Language

EN - EnglishDE - DeutschNL - NederlandsCA - CatalàES - EspañolFR - Français

Explore

  • News
  • Matches
  • Competitions
  • Club finder
  • Resources

Countries

  • Netherlands
  • Germany
  • Belgium
  • Spain
  • England
  • Argentina

Publication

  • About
  • Editorial
  • Authors
  • Contact

Contribute

  • Share photos
  • Share news
  • Report bugs
  • Careers
  • Donate to development

Legal

  • Legal Notice
  • Privacy Policy
  • Terms of Service
  • Cookie Policy
  • Data rights

Language

ENEnglishDEDeutschNLNederlandsCACatalàESEspañolFRFrançais

Social

© 2026 StickAtlas. Ribas Rovira SL / Piar Concept.

Multilingual, data-first field hockey coverage across countries and competitions.

Share photosShare newsReport bugsCareersDonate to development

Product feedback

Report something that is broken or off.

Use this route when a page fails, a flow breaks, a data surface looks wrong, or something simply feels inconsistent. Reports go into a private queue so product and editorial can review what slipped through.

Report bugs

Send a bug report or product issue directly to review.

Purpose: we use this data only to manage your request, reply to you, and keep a minimum compliance record of the submission.

I allow StickAtlas to store this bug report so the team can review it and follow up if needed.

Specific reports are easier to fix

A useful bug report usually includes the affected page, what you expected to happen, what happened instead, and any device or browser detail that might help reproduce it.

Point to the exact page or flow

Paste the URL, route, or section where the issue appears so the problem can be reproduced faster.

Describe expected vs actual behavior

A short comparison makes it easier to see whether the issue is visual, editorial, or technical.

Include context that helps reproduce it

Browser, device, screen size, logged-in state, or the last step you took can save time.