Back to results

As of 2025-06-02, Fvh Jars Chicago I received a Pass w/ Conditions on its most recent City of Chicago health inspection.

Fvh Jars Chicago I

CONDITIONAL
905 W Fulton Market, Chicago, IL 60607
West Loop · Chicago Dept. of Public Health · Last inspected 2025-06-02

Violations at most recent inspection

OBSERVED NO CITY OF CHICAGO FOOD SANITATION CERTIFICATE POSTED ON THE PREMISES. MANAGEMENT INSTRUCTED THAT A CERTIFIED FOOD MANAGER MUST BE PRESENT AT ALL TIMES WHILE TCS FOODS ARE BEING PREPARED OR SERVED. PRIORITY FOUN
priority violation
REPAIR THE HOT WATER HANDLE FOR THE EXPOSED HAND WASHING SINK IN THE REAR FOOD PREP AREA.
core violation
OBSERVED NO MECHANICAL VENTILATION FAN IN THE EMPLOYEE WASHROOM. MANAGEMENT INSTRUCTED TO INSTALL.
core violation
OBSERVED NO INSPECTION REPORT SUMMARY POSTED ON THE PREMISES. MANAGEMENT WAS GIVEN A COPY OF TODAY'S INSPECTION REPORT AND WAS INSTRUCTED TO POST IT IN PUBLIC VIEW. PRIORITY FOUNDATION VIOLATION 7-42-010(B). CITATION ISS
priority violation
Advertisement

Inspection history — tap to expand

Fvh Jars Chicago I health inspection FAQ

Has Fvh Jars Chicago I passed its most recent Chicago health inspection?

Fvh Jars Chicago I received a Pass w/ Conditions on its most recent City of Chicago health inspection, conducted on 2025-06-02. This reflects the restaurant's current status as tracked by the Chicago Department of Public Health -- GutCheck rebuilds this page from the city's live data feed, so it updates automatically as new inspections are recorded.

What violations did Fvh Jars Chicago I have at its last health inspection?

Inspectors recorded 4 violations at Fvh Jars Chicago I's most recent inspection on 2025-06-02, including 2 classified as Priority or Priority Foundation. Full violation text is listed on this page below.

When was Fvh Jars Chicago I last inspected by the City of Chicago?

Fvh Jars Chicago I was last inspected on 2025-06-02. GutCheck's data is sourced directly from the City of Chicago's public Food Inspections feed and rebuilt on every deploy, so this date reflects the most recent inspection on file at the time you're viewing this page.