TEXAS HOG DISPATCHOPERATORS & INDUSTRY · BEHIND THE WORK
Cost & Contracts

Why There Is No Honest ‘Average’ Hog-Removal Price

Public pricing examples use incompatible units, so a single average would describe nothing.

Record reviewed:
Aerial view of a rural Texas property showing a house, pasture with hogs, staged trap panels, a truck and trailer on a dirt drive, and a wooded creek line.
Because the published examples are not measuring the same thing. Some price a trap per month, some a day of equipment rental, some an animal, some a defined project, some travel, some a bounty, and some exchange access or rights to captured animals instead of cash. An average across incompatible units produces a number that describes none of them.

What the record shows

Units observed in public agreements and public program materials include, in no particular order:

  • Per trap, per month, as in the City of Kyle agreement, with defined travel terms.
  • Daily or weekly equipment rental, where the customer holds part of the work.
  • Per animal removed, which shifts risk toward the operator.
  • Project or package pricing for a defined scope and a defined end.
  • Travel or mobilization priced separately from field time.
  • Bounty style payments used by some public programs as an incentive rather than a service price.
  • No cost or reduced cost arrangements where access, or rights to captured animals, forms part of the consideration.
  • Hybrids that combine several of the above inside one agreement.

Why averaging destroys meaning

Each unit carries a different bundle: who supplies equipment, who checks it, who transports animals, who absorbs a slow week, who keeps the animals, and who carries insurance. Two agreements can price identically and describe opposite amounts of work.

The Kyle agreement is a clean illustration rather than a benchmark. Its monthly per trap structure, its travel terms, its retention of captured hog rights by the operator, and its staged setup and takedown at operator discretion all sit inside the same number. Change any one of them and the unit no longer means what it meant.

This is why the useful question is not what does removal cost. It is what unit is being quoted, and what is inside it.

An operator working late at a barn workbench reviewing trail camera images on a laptop beside notes, maps, camera gear, and a spare tire.

Questions that make a quote comparable

Understanding units is the goal here. These questions clarify scope without asking anyone to disclose proprietary methods.

  • What is the billing unit, and what period or quantity does it cover?
  • What is included: travel, setup, monitoring, daily checks, removal, disposition, documentation?
  • Who keeps or handles captured animals, and who arranges transport?
  • What ends the engagement, and what does closeout include?
  • What is excluded and billed separately?

No rates published here

This page deliberately publishes no rate, no price table, no statewide average, and no operator comparison. Individual commercial price figures are not featured, because the purpose is understanding units and scope rather than benchmarking or undercutting anyone's pricing.

Limits and Scope of This Evidence

  • The unit list is drawn from publicly available agreements and program materials, not from a survey of the market.
  • Public agreements reflect what one buyer negotiated at one time, including local conditions and competition.
  • Private pricing is not public, so no distribution of prices can be described from this record.

What This Page Does Not Claim

  • That any rate is typical, fair, recommended, or excessive.
  • That the Kyle structure is a model contract or a pricing guide.
  • That a statewide average price exists, or could be responsibly derived from these sources.
  • That Texas Hog Dispatch sets, collects, or influences operator pricing.

Sources

Record reviewed . Documents linked below were public at that date. Contract requirements belong to the buying jurisdiction named, not to operators generally.

Operator Perspective or Correction

If a document here is out of date, mischaracterized, or missing context, send the correction with its source to data@texashogdispatch.com. Field context from working operators is welcome. Nothing sent is published as an endorsement, and we do not publish proprietary methods, customer identities, property locations, or private price sheets.

Report a data error

Related Reading