You can move around with your keyboard
plus
minus
left
right
Drop pin on the map to start a new report
space
Press space again to adjust the location
space
Back to all reports

Grafitti on hoarding of Purelake development

Reported via desktop in the Graffiti category anonymously at 14:53, Saturday 5 February 2022

Sent to London Borough of Bexley less than a minute later. Report ref: 3291557.

There are several different tags on the outside of the hoarding surrounding the development at the old Co-operative site between Station Road and Greenwood Close.

RSS feed of updates to this problem Receive email when updates are left on this problem.

Updates

  • This case is currently being investigated.

    Further updates will follow.

    State changed to: Investigating

    Posted by London Borough of Bexley at 08:22, Monday 7 February 2022

  • Graffiti not removed 5/3/22

    Posted anonymously by a non-staff user at 14:07, Sunday 6 March 2022
    Still open, via questionnaire

  • Questionnaire filled in by problem reporter

    State changed to: Fixed

    Posted anonymously by a non-staff user at 16:58, Tuesday 5 April 2022

  • Graffiti not removed and more iis on it since the first report

    Posted anonymously by a non-staff user at 16:59, Tuesday 5 April 2022
    Still open, via questionnaire

  • Yesterday, 3/5/22 we walked past the Purelake hoarding and found that the part facing Greenwood Close and visible from the road had been painted over but the graffiti parallel with the long station boundary was still there. I feel this should be the responsibility of Purelake to cover the graffiti.

    Posted anonymously by a non-staff user at 08:00, Wednesday 4 May 2022
    Still open, via questionnaire

  • This case is currently being investigated.

    Further updates will follow.

    State changed to: Investigating

    Posted by London Borough of Bexley at 17:07, Wednesday 1 June 2022

  • Although the original problem was finally fixed, unfortunately, there is more graffiti now.

    State changed to: Fixed

    Posted anonymously by a non-staff user at 17:07, Wednesday 1 June 2022

This report is now closed to updates. You can make a new report in the same location.