Hinganghāt, Maharashtra, India

Silver Price

999 per gram ₹264.59
925 per gram ₹244.75
900 per gram ₹238.13

Last rate update: Mon, May 4, 2026 2:02 PM

Silver 999 price performance

▲ Up ₹0.49 (+0.2%) over 30 days

Calculation output

Line itemValue
Rate per gram₹264.59
Weight in grams10.000
Gold value₹2,645.90
Chargeable weight10.000
Making charge₹0.00
GST amount₹79.38
Total₹2,725.28

Recent rate history

Date Avg Price Status
May 04, 2026 ₹264.59 Verified
May 03, 2026 ₹264.59 Verified
May 02, 2026 ₹263.41 Verified
May 01, 2026 ₹264.85 Verified
Apr 30, 2026 ₹263.01 Verified
Apr 29, 2026 ₹262.49 Verified
Apr 28, 2026 ₹263.81 Verified
Apr 27, 2026 ₹265.14 Verified
Apr 26, 2026 ₹266.23 Verified
Apr 25, 2026 ₹263.72 Verified

If you’re tracking silver prices in Hinganghāt, Maharashtra, here’s a practical snapshot based on the latest available rates. As of 2026-05-03T21:52:07+00:00, silver at 999 purity is listed at 264.59, while 925 purity is 244.75 and 900 purity is 238.13. The provided figures show no recorded day-over-day percentage change for these purities at the time of the fetch (change_percent: 0 for 999, 925, and 900). For context, the recent history from 2026-04-04 through 2026-05-03 shows prices moving within a relatively tight band, with values such as 265.76 on 2026-04-04 and 263.41 on 2026-05-02, followed by 264.59 on 2026-05-03. Use these numbers to compare purity-specific pricing and to monitor short-term movement.

Market

Market pulse

The latest silver-price snapshot for Hinganghāt, Maharashtra (fetched 2026-05-03T21:52:07+00:00) shows 999 at 264.59, 925 at 244.75, and 900 at 238.13, with change_percent reported as 0 for each purity at fetch time. Looking at the recent history, prices have generally hovered around the low-to-mid 260s: for example, 265.76 on 2026-04-04, 262.98 on 2026-04-10, 266.33 on 2026-04-17, and 263.41 on 2026-05-02. On 2026-05-03, the value shown is 264.59, indicating a modest shift versus the prior day in the dataset.

Guide

Buyer playbook

When comparing silver options in Hinganghāt, Maharashtra, start by matching the purity to the rate you’re using. In the provided data, 999 is 264.59, 925 is 244.75, and 900 is 238.13 (all fetched 2026-05-03T21:52:07+00:00). Next, compare the current figure to the recent history to understand short-term movement—for instance, 263.41 on 2026-05-02 versus 264.59 on 2026-05-03. If you’re evaluating multiple listings, ensure they reference the same purity level and the same unit basis as the dataset. Finally, keep a simple record of the fetch timestamp and the purity you used, since the rates shown are time-specific and the dataset includes a consistent fetched_at value for the current snapshot.

Checklist

Local buying checklist

  1. Verify current rates.
  2. Check purity markings.
  3. Match the purity to the correct rate (999/925/900).
  4. Compare against the recent history dates (e.g., 2026-05-02 to 2026-05-03).
  5. Record the fetched_at timestamp used for the snapshot (2026-05-03T21:52:07+00:00).
  6. Confirm the listing uses the same unit basis as the provided rates.

Coverage snapshot

Active cities 1
States covered 32
Country pages 1

Frequently asked questions

  • What are the latest silver rates for Hinganghāt, Maharashtra? As of 2026-05-03T21:52:07+00:00: 999 = 264.59, 925 = 244.75, and 900 = 238.13.
  • Did the rates change at the time of the latest fetch? In the provided snapshot, change_percent is 0 for 999, 925, and 900.
  • What was the silver value on 2026-05-02 and 2026-05-03 (from the history)? The recent history shows 263.41 on 2026-05-02 and 264.59 on 2026-05-03.
  • How can I compare prices across different silver purities? Use the purity-specific rates from the snapshot: 999 (264.59), 925 (244.75), and 900 (238.13), and ensure listings match the same purity.
  • Where is the location referenced in these rates? The page context is Hinganghāt, Maharashtra, India.
  • Why is the fetched_at timestamp important? The rates are time-specific; the current snapshot is tied to 2026-05-03T21:52:07+00:00, so comparing later prices should use the corresponding fetch time.