top of page

Significant Porphyry Copper Potential at Tea Tree Prospect


  • Results from regional soil program and IP survey demonstrates extensive potential at Tea Tree - located in the north of the expanded 456 sq km Biloela project tenement package

  • Results at Tea Tree highlight a 2 km Cu-Au-Zn soil anomaly associated with 1 km gradient array IP chargeability anomaly and 25m @ 1.3 g/t Au, 1.5% Cu, 0.6% Zn (open) in assays resampling historical trenches

  • A second anomalous zone 200 m to the east of Tea Tree returned 1.1 km Cu-Zn soil anomaly associated with 1.4 km gradient array IP chargeability anomaly and historical rock chips of up to 23.0% Cu and 29.0% Zn

  • Potential for two Cu-Au-Zn mineralised zones at Tea Tree extending over 1 km each

  • New prospect identified at Tea Tree West with 1 km Cu-Au-Mo-Bi soil anomaly associated with bulls-eye magnetic high and radiometric potassium anomaly in area that has seen no previous exploration

  • Porphyry Cu deposit characteristics at Tea Tree West and skarn like Cu-Au-Zn mineralisation at Tea Tree highlight an extensive porphyry alteration system that is untested with drilling

Bindi Metals Limited (ASX: BIM, “Bindi” or the “Company”) is pleased to announce the results of the regional soil sampling and gradient array IP survey completed at the Tea Tree area, 15 km north of the Flanagan’s prospect and 2022 drill program (see Figure 8 for location), within the 456 sq km tenement package of the Biloela Project, Queensland (the Project).

Bindi Metals Executive Director, Henry Renou commented: “ Results from Tea Tree highlight the significant potential for a new porphyry Cu-Au system within the highly prospective Connors Arc terrain. This is a proven belt that hosts worldclass deposits such as the 8 Moz Mt Morgan gold-copper deposit. Extensive soil and IP anomalies at Tea Tree as well as the newly discovered zone at Tea Tree West are highly encouraging and represent impressive potential drill targets for Bindi.”


Couldn’t Load Comments
It looks like there was a technical problem. Try reconnecting or refreshing the page.
bottom of page