Askari Metals confirmed continuous mineralisation at its Uis project, with peak results of 6,670 ppm tin and 0.49% Li2O, as it targets a maiden resource in 2026.
Askari Metals (ASX: AS2) has confirmed continuous polymetallic mineralisation across the PS pegmatite target at its Uis project in Namibia, following the completion of a 14-trench, 272-metre exploration program. The results provide a structural foundation for the company’s upcoming drilling campaigns and its stated goal of defining a maiden resource for the project before the end of the calendar year. For investors, the data represents a transition from surface-level mapping to a more defined, drill-ready geological model.
The Phase 1 trenching program successfully exposed the PS pegmatite target over a 260-metre strike length at the surface, with a secondary parallel pegmatite extending for approximately 140 metres. These findings are significant because they validate the geological continuity required to justify larger-scale reverse circulation (RC) drilling. The presence of LCT-type (lithium-caesium-tantalum) indicators—specifically albite, coloured tourmaline, and green mica—suggests a high degree of fractionation within the pegmatite system, which is a primary prerequisite for identifying economically viable concentrations of lithium and associated metals.
Peak assay results from the trenching program included 6,670 parts per million (ppm) tin, 0.49% lithium oxide (Li2O), 465 ppm tantalum, 2,020 ppm rubidium, and 134 ppm caesium. While these surface grades are encouraging, the primary utility of this data is its role in refining the geometry of the ore body. By mapping the surface expression, Askari has reduced the uncertainty surrounding the orientation of the pegmatites, which should improve the hit rate for the planned RC drilling in the second half of 2026.
The current trenching results align with historical rock chip sampling, which previously returned values as high as 3.05% Li2O and 1.63% tin oxide. The consistency between these historical surface samples and the new trenching data suggests that the mineralisation is not merely a localized anomaly but a persistent feature of the PS target. Previous RC drilling campaigns at the site have already intercepted high-grade zones, including 4 metres at 0.16% tin oxide and 4 metres at 314 ppm tantalum oxide.
This historical context is crucial for understanding the risk profile of the Uis project. The company is not exploring a greenfield site with unknown geological potential; rather, it is systematically verifying the depth and scale of a system that has already demonstrated mineralisation across multiple phases of surface and subsurface work. The integration of these datasets is intended to de-risk the upcoming maiden resource estimation process.
Askari has outlined a clear operational sequence for the second half of 2026. The drilling program will prioritize the OP target before expanding to include the DP, PS, and K9 pegmatite targets. The K9 target is particularly notable as it is slated for its maiden diamond drilling campaign, reflecting its status as a spodumene-rich prospect.
For those tracking stock market analysis within the junior mining sector, the focus remains on the transition from exploration to resource definition. The company’s ability to move from trenching to a maiden resource estimate within a single calendar year is an aggressive timeline that relies on the structural integrity of the pegmatites identified in this phase.
Ultimately, the success of the Uis project will be measured by the company’s ability to convert these surface-level indications into a JORC-compliant resource. The current data provides the necessary confidence to proceed with the planned drilling, but the market will likely wait for the results of the H2 2026 campaign to confirm whether the mineralisation holds its grade at depth. The validation of the PS target is a necessary step, but the scale of the deposit remains the primary variable for long-term valuation.
AI-drafted from named sources and checked against AlphaScala publishing rules before release. Direct quotes must match source text, low-information tables are removed, and thinner or higher-risk stories can be held for manual review.