Names of Andijon Victims

by Nathan Hamm on 6/8/2005

B. Hamroev, “Family Names of 316 Victims at Andijon have been listed.”
Fergana.ru
Translated by David Walther

In an interview with the Moscow newspaper, “Novie Izvestiya,” […] a member of ‘Birlik,’ Bakhrom Hamroev, announced his estimation of the number of Andijon victims.

“We are conducting—together with “Memorial” and other human rights organizations—an investigation of the events in Andijon,” said Hamroev.

“We have established a list of the names of 316 victims, of whom 76 are girls between 8 and 14 years of age. Among those who came under fire were many accidental passers-by who had the misfortune of being near the protesters. The names of 630 others, killed and subsequently removed from Andijon by airplane, remain unknown. There is a suggestion that the total number of victims could reach 1500 people.”

You can read the full text of the interview [in Russian] at the newspaper’s site, www.newizv.ru.

[note that this little article still doesn’t indicate that a list has actually been released to the media, but also note it includes a charge that victims’ bodies were removed by air from the town, which might explain where some of the graves are, or rather, where they are not].


Subscribe to receive updates from Registan

This post was written by...

– author of 2991 posts on 17_PersonNotFound.

Nathan is the founder and Principal Analyst for Registan, which he launched in 2003. He was a Peace Corps Volunteer in Uzbekistan 2000-2001 and received his MA in Central Asian Studies from the University of Washington in 2007. Since 2007, he has worked full-time as an analyst, consulting with private and government clients on Central Asian affairs, specializing in how socio-cultural and political factors shape risks and opportunities and how organizations can adjust their strategic and operational plans to account for these variables. More information on Registan's services can be found here, and Nathan can be contacted via Twitter or email.

For information on reproducing this article, see our Terms of Use

Previous post:

Next post: