Back to results
Closed

City inspectors recorded this establishment as out of business on 2023-01-23. Its inspection history is kept below in full — the record does not stop being true because the business shut. The city publishes no reason for a closure, and none is inferred here. A licence can be reinstated; if this one is inspected and graded again, the notice clears on the next rebuild.

As of 2022-03-15, Mariscos El Malecon #2 passed its most recent City of Chicago health inspection.

Mariscos El Malecon #2

PASS
3537 E 106th St , Chicago, IL 60617
South Chicago · Chicago Dept. of Public Health · Last inspected 2022-03-15
License re-inspection
Map loading

Violations at most recent inspection

OBSERVED TORN GASKETS ON REACH IN PREP COOLER. INSTRUCTED MANAGER TO REPAIR AND MAINTAIN.
core violation
OBSERVED LEAKING FAUCET FIXTURES AT 3 COMPARTMENT SINK AND HAND SINK IN PREP AREA. INSTRUCTED MANAGER TO REPAIR AND MAINTAIN.
core violation
OBSERVED FOOD SERVICE MANAGER WITH OUT ALLERGEN TRAINING. INSTRUCTED MANAGER TO MEET REQUIREMENT AND MAINTAIN.
core violation

Inspection history — tap to expand

20222 inspections

Mariscos El Malecon #2 health inspection FAQ

Has Mariscos El Malecon #2 passed its most recent Chicago health inspection?

Mariscos El Malecon #2 passed its most recent City of Chicago health inspection, conducted on 2022-03-15. 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 Mariscos El Malecon #2 have at its last health inspection?

Inspectors recorded 3 violations at Mariscos El Malecon #2's most recent inspection on 2022-03-15. Full violation text is listed on this page below.

When was Mariscos El Malecon #2 last inspected by the City of Chicago?

Mariscos El Malecon #2 was last inspected on 2022-03-15. 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.