[6] Torpedo Novgorod 1-3 Lokomotiv Yaroslavl [7] 2017-01-19 16:00
Stadium: Trade Union Sport Palace Round: 1
Head to Head
| KHL | 2016/12/24 14:00 | Torpedo Novgorod v Lokomotiv Yaroslavl | L | 1-3 |
| KHL | 2016/09/18 14:30 | Lokomotiv Yaroslavl v Torpedo Novgorod | W | 0-3 |
| KHL | 2016/09/16 16:30 | Lokomotiv Yaroslavl v Torpedo Novgorod | W | 1-2 |
| Venskabskampe (kun ordinær spilletid) | 2016/08/04 16:00 | Torpedo Novgorod v Lokomotiv Yaroslavl | W | 5-2 |
| KHL | 2016/01/20 16:00 | Torpedo Novgorod v Lokomotiv Yaroslavl | L | 1-2 |
| KHL | 2016/01/11 16:30 | Lokomotiv Yaroslavl v Torpedo Novgorod | L | 3-0 |
| KHL | 2015/09/20 14:00 | Lokomotiv Yaroslavl v Torpedo Novgorod | L | 3-1 |
| KHL | 2015/08/25 16:00 | Torpedo Novgorod v Lokomotiv Yaroslavl | W | 3-2 |
Home History
| KHL | 2017/01/15 12:00 | Metallurg Magnitogorsk v Torpedo Novgorod | L | 3-2 |
| KHL | 2017/01/12 14:00 | Salavat Ulaev UFA v Torpedo Novgorod | W | 1-6 |
| KHL | 2017/01/10 14:00 | Traktor Chelyabinsk v Torpedo Novgorod | W | 2-3 |
| KHL | 2017/01/08 11:00 | Barys Astana v Torpedo Novgorod | W | 1-3 |
| KHL | 2017/01/06 12:00 | Avtomobilist Yekaterinburg v Torpedo Novgorod | W | 1-2 |
| KHL | 2017/01/04 11:30 | HC Yugra v Torpedo Novgorod | W | 0-2 |
| KHL | 2016/12/26 16:00 | Torpedo Novgorod v HC Vityaz | W | 3-2 |
| KHL | 2016/12/24 14:00 | Torpedo Novgorod v Lokomotiv Yaroslavl | L | 1-3 |
Away History
| KHL | 2017/01/16 16:00 | Lokomotiv Yaroslavl v Lada Togliatti | W | 4-2 |
| KHL | 2017/01/14 14:00 | Lokomotiv Yaroslavl v Neftekhimik Niznekamsk | W | 3-1 |
| KHL | 2017/01/12 16:30 | Lokomotiv Yaroslavl v AK Bars Kazan | W | 2-1 |
| KHL | 2017/01/09 16:00 | Lokomotiv Yaroslavl v Dinamo Riga | W | 3-1 |
| KHL | 2017/01/07 11:00 | Avangard Omsk v Lokomotiv Yaroslavl | L | 3-2 |
| KHL | 2017/01/05 10:00 | Metallurg Novokuznetsk v Lokomotiv Yaroslavl | W | 1-2 |
| KHL | 2017/01/03 10:30 | Sibir Novosibirsk v Lokomotiv Yaroslavl | L | 3-2 |
| KHL | 2016/12/29 16:30 | SKA St Petersburg v Lokomotiv Yaroslavl | W | 1-2 |
We're selling API, please Contact Us