License and other fees for race meets not subject to ORS 462.057 and 462.062
All licensees of race meets except those subject to ORS 462.057 (License and other fees and purses) and 462.062 (Fees and other payments by licensees of horse race meets not subject to ORS 462.057) shall make payments as follows:
(1) License fee – $100 per racing day, payable to the Oregon Racing Commission.
(2) Percentage of gross mutuel wagering payable to the commission – 1.6 percent.
(3) Percentage of gross mutuel wagering on greyhound races payable to the Oregon Greyhound Breeders Association, Incorporated – 0.5 percent for purse supplements for owners of Oregon bred greyhounds, to be apportioned among the owners, in accordance with the rules of the commission and subject to approval by the commission, in the same ratio that each owner’s purses for Oregon bred greyhounds for the race meet bears to the total purses for Oregon bred greyhounds for the race meet. Subject to the prior written approval of the commission, the Oregon Greyhound Breeders Association, Incorporated, may use a portion of the funds received pursuant to this section and ORS 462.057 (License and other fees and purses) (1)(d)(B) to offset expenses for receipt, accounting, handling and payment of those funds.
(4) To a special fund to be used primarily for the development and operation of a training track and related facilities upon which to train greyhounds – 0.1 percent. All such funds shall be retained by the licensee in a separate account from all other funds and no disbursements or transfers shall be made therefrom without prior approval of the commission. All physical improvements paid from such funds shall satisfy reasonable fire, health, quality and construction standards established or approved by the commission. Unless the commission provides otherwise, such improvements shall be made on the race course of the race meet licensee. [1969 c.356 §8; 1975 c.550 §4; 1977 c.855 §8; 1979 c.698 §3; 1981 c.544 §6; 1987 c.413 §21; 1993 c.682 §3; 1996 c.15 §1]
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.