> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/standards-by-market.md).

# Standards by Market

Find electric-fence installation standards and energizer safety test certificates by market.

The per-market fence-installation standard, plus the IEC 60335-2-76 energizer safety test certificates.

| Market         | Standard      |
| -------------- | ------------- |
| Australia / NZ | AS/NZS 3016   |
| UK             | BS1722-17     |
| South Africa   | SANS10222-3   |
| China          | GB/T 7946     |
| Europe         | EN60335-2-76  |
| International  | IEC60335-2-76 |

**Gallagher controllers comply with:** IEC 60335-1 and IEC 60335-2-76.

### AU-specific

* Energy Safe Victoria requires non-prescribed certification for electric fences in Victoria
* AS/NZS 3016 governs installation requirements

### IEC 60335-2-76 - fence energizer safety (test certificates)

IEC 60335-2-76 covers the safety of electric fence energizers (rated voltage 250 V or less) used to electrify or monitor agricultural, domestic, feral-animal-control, and security fences. It sits under the general appliance-safety standard IEC 60335-1. **The Gallagher F-Series Fence Controllers are tested by the laboratory to comply** with this standard and its amendments.

| Generation              | Products                                         | Test evidence                                                                                                                                                                                                                                                                 |
| ----------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **F5x / F6x** (current) | G21923/33/35/43/53/55 Fence Controllers + MK PSU | [Certificate (valid 2026-02-27 to 2031-02-27)](https://media.gallagher.com/asset/f6f8b318-b784-4b11-be83-7412dc918495/Certificate-POC-pdf.pdf) · [Test report front page (2025-11-11)](https://media.gallagher.com/asset/46f39508-7cf5-458b-8d1f-89be2e1f56f4/2300-0-pdf.pdf) |
| **F3x / F4x** (legacy)  | G21920/21, G21940/41, F31/F32                    | Legacy safety reports are available on request.                                                                                                                                                                                                                               |

*The standards list above is confirmed against the SecHub Compliance & Reference source (IEC page and the Perimeter International Code of Practice page).*

***

🔗 **Related**

* International Code of Practice (INTCOP 7.1) · Critical Distances Reference


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/deployment-resources/security-and-compliance/perimeter-fence-compliance/standards-by-market.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.