HEALTHMONITOR SYSTEM CONTEXT ============================= PURPOSE: This system monitors a person living alone. The primary concern is undetected inactivity — ensuring the person is not in distress for an extended period without anyone knowing. People close to this individual have previously been found deceased days after the fact. This system exists to prevent that. DATA FORMAT: Each sensor record: SENSORNAME, count, DD-Mon-HH:MM count = number of motion detections in that 10-minute interval count = 0 means no motion was detected during that interval Sensors post every 10 minutes continuously, even when quiet (count = 0). Door events: DOORNAME, 8, DD-Mon-HH:MM (8 means the door was opened) SENSORS INSTALLED: LIVRM-KTCHN1 Living room and kitchen area — primary daytime activity zone BED-BATH-RM2 Bedroom and bathroom area — sleep and morning routine CAR3 Motion sensor mounted in vehicle — detects activity in or near car DOOR Tilt switch on main entry door — fires on door movement Note: cannot distinguish opening from closing GAP-FIRST OUTING DETECTION (replaces door-first approach): For each day, scan for stretches with no reading from either indoor sensor (LIVRM-KTCHN1 or BED-BATH-RM2) for 40 minutes or more (4+ consecutive missed 10-minute readings). Ignore anything under 40 minutes — normal lulls, sitting still, reading, etc. do not need to be reported. Readings land on a 10-minute grid, but the two sensors are not phase-aligned with each other (one may report on :00/:10/:20, the other on :01/:11/:21). When measuring a gap, snap all readings to their 10-minute slot first and look for slots where NEITHER sensor reported — don't measure raw time between individual readings, or phase offset creates false small gaps. Classify each gap found by what's around it: Under 40 minutes: not reportable — just inactivity. 40 min to ~3 hours, WITH a door event on both ends (or one right before the gap and one right after): a normal outing. Barry does not walk anywhere for exercise — his back limits him to about 3-4km on foot, so a walk explains only very short trips (to the parking lot, to a neighbor's, to the mailbox). For anything in this range, the likely explanation is: - CAR3 activity during the gap: he drove. - No CAR3 activity, warm/dry weather: he biked (up to ~25km, very common in summer). - No CAR3 activity, cold/wet/icy weather: likely he got a ride from someone (e.g. Bill) rather than biked or walked, since a walk that long doesn't fit his mobility. Check current Kingston weather to help decide between bike vs. car vs. ride. 40 min to ~3 hours, with NO door event on either side: flag as unexplained inactivity. Note the exact window and day. Don't assume it's nothing, but don't panic either — mention it plainly so a caregiver can ask Barry what he was doing. 3-4+ hours, WITH doors on both sides: a longer outing (e.g. hospital visit, full day out with Ken/Bill/Mara). Note the door times and any CAR3 activity, and reference any caregiver note that may explain it. 3-4+ hours, with NO door event on either side: the real warning sign. Call this out clearly as requiring follow-up — this is the pattern the whole system exists to catch. For each day's report, list only the 40-min+ gaps found (skip anything shorter). For each: the day and time window, length, doors before/after (or "none"), and the classification above. Note on data compression in this HealthMonitorAI export: This dataset uses tiered storage on an ESP32 with limited space — recent records (roughly the last 2 weeks relative to export time) are logged at full 10-minute resolution, while older records get periodically compressed into fewer, larger summary entries to save space. When analyzing this data, don't treat raw record count per day/period as a proxy for activity level — compare summed counts instead, since compression preserves totals but collapses how many entries they're spread across. A sharp jump in records-per-day or a drop in average-count-per-record at some date boundary is very likely a compression-tier artifact, not a real behavioral change, and should be checked against summed totals before being reported as a finding. There has also been a history of sporadic data loss (an agent deleting raw records before summaries were durably confirmed) which has since been fixed — treat any anomaly in this reconstructed window with that history in mind, and don't assume gaps or "quiet stretches" reflect real inactivity without corroborating signals (door events, notes, etc.), since they may simply be missing data. EMBEDDED NOTES: Lines marked ***note*** are caregiver annotations entered manually. Treat these as ground truth — they explain context the sensors cannot capture. They may describe outings, health events, schedule changes, or location. WHAT FOLLOWS: The client profile for this specific person appears next, followed by specific analysis instructions if a report format was selected. If no instructions follow, analyse the data openly and freely. === CLIENT PROFILE === CLIENT PROFILE ============== NAME: Barry AGE: 86 SEX: Male DWELLING: Apartment, Kingston ON LIVES ALONE: Yes VEHICLE: Parks in apartment parking lot outside the building NORMAL DAILY PATTERN: Active throughout the day. Sleep roughly 10pm to 7am - indoor sensors quiet during this window is expected and normal. Car use varies - could be daily or several days between trips. Overnight bathroom/bedroom sensor blips through the night are normal and expected - this is not something to flag or comment on unless a night looks meaningfully more fragmented or restless than the rest of the week. PELOTON WORKOUT PATTERN: When LIVRM-KTCHN1 shows high-count peaks of 1,300-1,800+ motion detections in a 10-minute interval, this is Barry on the Peloton bike. Identify these clearly in any analysis. Note frequency, timing (morning vs evening), duration (consecutive high-count windows), and any change in consistency over the period reviewed. During winter months this is attempted daily. SENSOR ROLES (interpret by role, not by fixed name): Treat sensors by what they do - "the car sensor," "the main daytime activity sensor," "the sleep-area sensor," "the door sensor" - rather than assuming a specific name will always be present. Barry occasionally reconfigures, renames, or swaps sensor hardware (e.g. a portable sensor taken to another location for a period), and the roles above should still apply correctly to whatever is currently reporting, without needing an update every time a name changes. CONCERN FLAG IS NOT A CONCLUSION: The chip's own "concern level" status (shown in exports as "Last known status") is a simple, dumb timer - it only means "no sensor has posted in over N hours." It is not itself an interpretation and should never be treated as one. Your own reasoning over the actual data and notes is the real analysis - the chip's flag is just a basic liveness check, nothing more. DAY OF WEEK: Always state the day of week for every date referenced in your analysis. Never use relative terms like "yesterday" or "two days ago" - always use full date and day of week. Use the report's generation timestamp to calculate the correct day of the week. Never assume or hardcode it. REPORT ORDER: For any multi-day report, always present days in chronological order, oldest day first, ending with the most recent day. Never present days newest-first or in any other order. BEFORE FINALIZING YOUR REPORT - MANDATORY CHECKLIST: For every day covered in the report, explicitly check the data against each of these patterns before writing that day's narrative - don't rely on noticing them naturally while summarizing, actively check for them: 1. Peloton range (1,300-1,800+ in a single 10-minute LIVRM-KTCHN1 reading) - if present, name it as Peloton use explicitly, even on an otherwise busy or ordinary-looking day. 2. Gap-first outing check (see sys_context.txt, "Gap-First Outing Detection") - for every day, scan for 40+ minute stretches where neither indoor sensor reported, and classify each one using that method (door on both sides = outing, name the likely mode of travel; no door on either side = flag as unexplained). Run this for every gap found, not just ones near a door event you already noticed. Run this check for every single day in the window, not just days that look unusual at a glance - a busy day can still contain a missed Peloton session or a short outing worth naming. If neither pattern applies to a given day after checking, no need to say so explicitly - just don't skip the check. === PERMANENT NOTES === Stable facts about this person. Consider when analysing sensor data. 07-Mar-2026 18:34 - The car noise floor should be set to 600. Below this is ambient level for apt parking lot - rain is the specific known cause of these false low-level triggers, not actual car use. Readings at or below 600 during rain should not be read as driving activity. === END CLIENT PROFILE === === CURRENT STATUS === Generated: 12-Sep-2026 15:07:39 EDT Export window: last 3 days Concern Level: UNKNOWN SENSOR HARDWARE STATUS (12-Sep-2026 15:07:39 EDT): 4 of 5 sensors operational. Not responding: WSGR15 (offline 3196min) === REPORT INSTRUCTION === No specific report format has been requested. Please analyse this data openly and freely. DATE AND TIME: State the day of week, full date, and time at the top of this report. Reference all events using absolute date and time (e.g. Monday March 2 at 14:30). Never use relative terms like "yesterday" or "two days ago" — these become ambiguous when a report is read hours after it was generated. WAKING DAY: When interpreting "today" or "yesterday", use the person's waking day — not calendar midnight-to-midnight boundaries. LOCATION: You MUST include a dedicated section with the exact heading "Likely Location" — do not fold this into other sections or narrative. State your conclusion first, then your reasoning. Use all available evidence: indoor sensor activity, door events, CAR1 activity, and any ***note*** entries. DAY OF WEEK: Consider the day of week when interpreting patterns. Habits and routines vary by day. Note anything inconsistent with what you know about this person's typical weekly rhythm. Look for anything noteworthy - patterns, anomalies, correlations between sensors, changes compared to earlier periods in the data. Consider: - Is the daily routine consistent or has something shifted? - Are sleep patterns normal for this person? - Is there anything a caregiver should know even if they did not think to ask? - Any single event or gap that stands out? Do not limit yourself to obvious health concerns. If the data suggests something unexpected, say so. Keep the response concise but flag anything genuinely notable. Note on clinical-format demo reports for this system: If asked to generate output formatted like a real clinical document (headers such as "Clinical Follow-Up Assessment Note," risk-stratification tiers, a bolded visit-recommendation verdict), always place an unmistakable disclaimer before the content and repeat it at the end, stating clearly that the output is test/demonstration material, was not produced or reviewed by a licensed clinician, and must not be used to make or defer any real care decision. This is necessary because that document format borrows clinical authority through its structure and tone — without a persistent, copy-paste-surviving disclaimer, a reader or a future production version of the software could mistake sensor-pattern narration for actual medical judgment. Do not soften this requirement even when the request frames the report as internal testing. ============================================================== === END INSTRUCTION === === ACTIVITY LOG - LAST 3 DAYS === Format: Sensor,Count,Timestamp (Notes always included.) ***note***,Read the Monday Wednesday and Friday get togethers with Ken and Bill presently Ken is in the hospital and will be there for at least a week or more. I will be visiting him Monday Wednesday and Friday as per usual but either will be biking or going with Bill so I will not be using the car I will let you know when Ken is home and we visit in the regular manner,06-Aug-23:14 ***note***,Barry has a foot doctor appointment Monday August 10th at 8:30 a.m.,06-Aug-23:16 ***note***,Barry and ClaudeCode reconstructed date going back to Feb. This may include some data hickups; software changes etc. Let's mark today as a stable software checkpoint and treat data after this date as more like production results. ,07-Aug-14:29 ***note***,Barry has been able to do a complete restore of the data accidental deleted. There are gaps and such here and there as we developed the system but should be more stable from now on.,07-Aug-15:44 ***note***,I checked with someone who said Barry was going to go out sometime in the morning pick up Mara drive to Nappanee have lunch and then drive back to her place and probably be there for supper home early evening ,09-Aug-18:56 ***note***,Barry said it's not confirmed but Ken should be coming home to his house to be looked after by his daughter she plans to pick him up at 4:00 p.m. on Sunday and Barry and Bill plan to visit him there at home on Monday and also on Wednesday and perhaps that would be standard for a short bit Barry will use his bicycle if weather is permitting to be at Ken's around 9:00 a.m. in the morning on Monday Wednesday Friday things may change daily because it depends on Ken's health,09-Aug-18:58 ***note***,Barry has a foot doctor appointment Monday August 10th at 8:30 a.m.,10-Aug-00:00 ***note***,Ken is home from the hospital; Barry and Bill are resuming regular Mon; Wed; Friday morning visits. Barry will bike to Ken's if WX is suitable (check Wx in Kingston; ON). If Wx unsuitable he will take the car. This should explain door and and activity levels each Mon; Wed; and Friday between roughly 8:30am to 1:30pm.,14-Aug-15:21 ***note***,Barry did not attend KAREX this morning. He will be going to Mara's for supper this evening and returning later in the evening. — Elon (Barry's Assistant),15-Aug-12:23 ***note***,Barry plans to cut Ken's grass tomorrow during a regular Mon;Wed;Friday visit. He will bike if the WX is good. ,16-Aug-12:05 ***note***,Barry is leaving home in a few minutes to bike to the Lake Ontario park for a picnic lunch. Expected to be gone a couple of hours.,16-Aug-13:28 ***note***,The elevator is on service and Barry cannot get his bike out. He will be remaining at home. Please disregard previous note.,16-Aug-13:47 ***note***,Sunday; August 16 — An unusually long and sustained block from roughly 16:10–18:40 (about 2.5 hours) with mostly high motion counts and one interval hitting 1;613. This observation was traced to a fan that was place where it effected Doppler readings. Disregard this unusual data in your reporting.,20-Aug-10:42 ***note***,Sunday August 16 16:10-18:40: Sustained high activity during this window was caused by a fan placed in line of fire of the Doppler sensor (air circulation/oscillation triggering false motion counts). Fan was removed. This is a data artifact and does not reflect actual activity.;16-Aug-18:45,20-Aug-10:53 ***note***,August 26; 2026 - Emergency trip to hospital ER with Ken and his daughter (12:28 AM - ~2:53 AM). Extended absence explains inactivity detection and subsequent clearance when returned home. System working as designed.,26-Aug-11:33 ***note***,"Barry away from Kingston apartment Aug 31 - Sep 11; staying at cottage. Kitchen/living; bedroom; and door sensors expected quiet during this period - normal; not a concern. WSGR (cottage) is the active sensor for this window,30-Aug-17:39 ***note***,the cottage sensors are being tested in the Apt living room until Monday morning and will be packed up and transported to the cottage by evening ,30-Aug-21:32 ***note***,There is no door hooked up at the cottage so there won't be any cottage door activity. ,05-Sep-16:52 WSGR15,155,09-Sep-15:11 WSGR15,229,09-Sep-15:21 WSGR15,46,09-Sep-15:41 WSGR15,67,09-Sep-15:51 WSGR15,89,09-Sep-16:01 WSGR15,128,09-Sep-16:51 WSGR15,200,09-Sep-17:01 WSGR15,216,09-Sep-17:11 WSGR15,545,09-Sep-17:21 WSGR15,421,09-Sep-17:31 WSGR15,144,09-Sep-17:41 WSGR15,390,09-Sep-17:51 WSGR15,361,09-Sep-18:01 WSGR15,98,09-Sep-18:21 WSGR15,94,09-Sep-18:31 WSGR15,167,09-Sep-18:41 WSGR15,66,09-Sep-18:51 WSGR15,209,09-Sep-19:01 WSGR15,87,09-Sep-19:11 WSGR15,41,09-Sep-19:21 WSGR15,32,09-Sep-19:31 WSGR15,67,09-Sep-19:41 WSGR15,34,09-Sep-19:51 WSGR15,78,09-Sep-20:01 WSGR15,424,09-Sep-20:11 WSGR15,417,09-Sep-20:21 WSGR15,727,09-Sep-20:31 WSGR15,676,09-Sep-20:41 WSGR15,425,09-Sep-20:51 WSGR15,464,09-Sep-21:01 WSGR15,280,09-Sep-21:11 WSGR15,60,09-Sep-21:21 WSGR15,57,09-Sep-21:31 WSGR15,49,09-Sep-21:41 WSGR15,33,09-Sep-21:51 WSGR15,51,09-Sep-22:01 WSGR15,47,09-Sep-22:11 WSGR15,96,09-Sep-22:21 WSGR15,210,09-Sep-22:31 WSGR15,49,09-Sep-22:41 WSGR15,449,09-Sep-22:51 WSGR15,141,09-Sep-23:01 WSGR15,200,09-Sep-23:11 WSGR15,34,09-Sep-23:21 WSGR15,54,09-Sep-23:31 WSGR15,50,10-Sep-00:11 WSGR15,25,10-Sep-03:21 WSGR15,24,10-Sep-04:01 WSGR15,32,10-Sep-05:41 WSGR15,47,10-Sep-07:21 WSGR15,46,10-Sep-07:51 WSGR15,98,10-Sep-08:11 WSGR15,161,10-Sep-08:21 WSGR15,133,10-Sep-08:31 WSGR15,310,10-Sep-08:41 WSGR15,39,10-Sep-08:51 WSGR15,331,10-Sep-09:01 WSGR15,85,10-Sep-09:41 WSGR15,218,10-Sep-09:51 BED-BATH-RM2,35,10-Sep-11:20 CAR3,477,10-Sep-12:21 CAR3,696,10-Sep-13:21 CAR3,686,10-Sep-13:31 CAR3,596,10-Sep-13:41 CAR3,631,10-Sep-13:51 CAR3,628,10-Sep-14:01 DOOR,8,10-Sep-14:14 LIVRM-KTCHN1,361,10-Sep-14:20 BED-BATH-RM2,25,10-Sep-14:20 LIVRM-KTCHN1,512,10-Sep-14:30 BED-BATH-RM2,782,10-Sep-14:30 LIVRM-KTCHN1,919,10-Sep-14:40 BED-BATH-RM2,192,10-Sep-14:40 LIVRM-KTCHN1,1216,10-Sep-14:50 BED-BATH-RM2,245,10-Sep-14:50 LIVRM-KTCHN1,219,10-Sep-15:00 BED-BATH-RM2,100,10-Sep-15:00 LIVRM-KTCHN1,82,10-Sep-15:10 BED-BATH-RM2,215,10-Sep-15:10 LIVRM-KTCHN1,70,10-Sep-15:20 BED-BATH-RM2,145,10-Sep-15:20 LIVRM-KTCHN1,172,10-Sep-15:30 BED-BATH-RM2,1611,10-Sep-15:30 LIVRM-KTCHN1,345,10-Sep-15:40 BED-BATH-RM2,954,10-Sep-15:41 LIVRM-KTCHN1,226,10-Sep-15:50 LIVRM-KTCHN1,290,10-Sep-16:00 BED-BATH-RM2,22,10-Sep-16:00 LIVRM-KTCHN1,160,10-Sep-16:10 BED-BATH-RM2,52,10-Sep-16:10 BED-BATH-RM2,37,10-Sep-16:30 LIVRM-KTCHN1,58,10-Sep-16:40 BED-BATH-RM2,24,10-Sep-16:40 LIVRM-KTCHN1,97,10-Sep-16:50 LIVRM-KTCHN1,105,10-Sep-17:00 DOOR,8,10-Sep-17:09 LIVRM-KTCHN1,277,10-Sep-17:10 BED-BATH-RM2,162,10-Sep-17:11 LIVRM-KTCHN1,52,10-Sep-18:10 BED-BATH-RM2,242,10-Sep-18:10 LIVRM-KTCHN1,221,10-Sep-18:20 LIVRM-KTCHN1,81,10-Sep-18:30 LIVRM-KTCHN1,158,10-Sep-18:40 LIVRM-KTCHN1,267,10-Sep-18:50 LIVRM-KTCHN1,253,10-Sep-19:00 LIVRM-KTCHN1,192,10-Sep-19:10 LIVRM-KTCHN1,34,10-Sep-19:20 LIVRM-KTCHN1,35,10-Sep-19:30 LIVRM-KTCHN1,204,10-Sep-19:40 BED-BATH-RM2,78,10-Sep-19:40 LIVRM-KTCHN1,391,10-Sep-19:50 BED-BATH-RM2,52,10-Sep-19:50 LIVRM-KTCHN1,50,10-Sep-20:00 BED-BATH-RM2,32,10-Sep-20:00 LIVRM-KTCHN1,95,10-Sep-20:10 LIVRM-KTCHN1,31,10-Sep-20:20 BED-BATH-RM2,16,10-Sep-20:20 LIVRM-KTCHN1,59,10-Sep-20:30 LIVRM-KTCHN1,115,10-Sep-20:40 BED-BATH-RM2,46,10-Sep-20:40 LIVRM-KTCHN1,184,10-Sep-20:50 LIVRM-KTCHN1,46,10-Sep-21:00 LIVRM-KTCHN1,53,10-Sep-21:10 LIVRM-KTCHN1,49,10-Sep-21:20 LIVRM-KTCHN1,43,10-Sep-21:30 LIVRM-KTCHN1,106,10-Sep-21:40 LIVRM-KTCHN1,126,10-Sep-21:50 LIVRM-KTCHN1,235,10-Sep-22:00 LIVRM-KTCHN1,196,10-Sep-22:10 BED-BATH-RM2,118,10-Sep-22:11 LIVRM-KTCHN1,191,10-Sep-22:20 BED-BATH-RM2,796,10-Sep-22:20 LIVRM-KTCHN1,73,10-Sep-22:30 LIVRM-KTCHN1,244,10-Sep-22:40 LIVRM-KTCHN1,479,10-Sep-22:50 BED-BATH-RM2,412,10-Sep-22:50 LIVRM-KTCHN1,157,10-Sep-23:00 LIVRM-KTCHN1,42,10-Sep-23:10 LIVRM-KTCHN1,61,10-Sep-23:30 LIVRM-KTCHN1,300,10-Sep-23:40 BED-BATH-RM2,353,10-Sep-23:50 LIVRM-KTCHN1,147,10-Sep-23:51 BED-BATH-RM2,183,11-Sep-00:00 BED-BATH-RM2,88,11-Sep-00:10 BED-BATH-RM2,17,11-Sep-00:20 BED-BATH-RM2,21,11-Sep-00:40 BED-BATH-RM2,75,11-Sep-00:50 BED-BATH-RM2,29,11-Sep-01:10 BED-BATH-RM2,251,11-Sep-01:20 BED-BATH-RM2,58,11-Sep-02:30 BED-BATH-RM2,318,11-Sep-02:40 BED-BATH-RM2,211,11-Sep-03:00 BED-BATH-RM2,40,11-Sep-03:10 BED-BATH-RM2,26,11-Sep-04:00 BED-BATH-RM2,28,11-Sep-04:10 BED-BATH-RM2,52,11-Sep-04:21 BED-BATH-RM2,19,11-Sep-04:30 BED-BATH-RM2,43,11-Sep-04:40 BED-BATH-RM2,177,11-Sep-04:50 BED-BATH-RM2,113,11-Sep-05:00 BED-BATH-RM2,48,11-Sep-05:10 BED-BATH-RM2,66,11-Sep-05:20 BED-BATH-RM2,88,11-Sep-06:10 BED-BATH-RM2,43,11-Sep-06:20 BED-BATH-RM2,74,11-Sep-06:30 BED-BATH-RM2,26,11-Sep-06:40 BED-BATH-RM2,71,11-Sep-06:50 BED-BATH-RM2,19,11-Sep-07:00 BED-BATH-RM2,26,11-Sep-07:10 BED-BATH-RM2,39,11-Sep-07:20 BED-BATH-RM2,39,11-Sep-07:30 BED-BATH-RM2,138,11-Sep-07:41 BED-BATH-RM2,169,11-Sep-07:50 BED-BATH-RM2,52,11-Sep-08:00 BED-BATH-RM2,19,11-Sep-08:10 BED-BATH-RM2,88,11-Sep-08:30 BED-BATH-RM2,112,11-Sep-08:40 LIVRM-KTCHN1,54,11-Sep-08:50 BED-BATH-RM2,267,11-Sep-08:50 LIVRM-KTCHN1,744,11-Sep-09:00 LIVRM-KTCHN1,159,11-Sep-09:10 BED-BATH-RM2,127,11-Sep-09:11 LIVRM-KTCHN1,346,11-Sep-09:20 BED-BATH-RM2,138,11-Sep-09:21 LIVRM-KTCHN1,277,11-Sep-09:30 LIVRM-KTCHN1,409,11-Sep-09:40 LIVRM-KTCHN1,246,11-Sep-09:50 LIVRM-KTCHN1,177,11-Sep-10:00 LIVRM-KTCHN1,493,11-Sep-10:10 BED-BATH-RM2,142,11-Sep-10:10 LIVRM-KTCHN1,509,11-Sep-10:20 LIVRM-KTCHN1,485,11-Sep-10:30 LIVRM-KTCHN1,470,11-Sep-10:40 BED-BATH-RM2,41,11-Sep-10:40 LIVRM-KTCHN1,897,11-Sep-10:50 LIVRM-KTCHN1,655,11-Sep-11:00 LIVRM-KTCHN1,886,11-Sep-11:10 LIVRM-KTCHN1,415,11-Sep-11:20 LIVRM-KTCHN1,832,11-Sep-11:30 LIVRM-KTCHN1,693,11-Sep-11:40 BED-BATH-RM2,101,11-Sep-11:40 LIVRM-KTCHN1,462,11-Sep-11:50 BED-BATH-RM2,462,11-Sep-11:50 LIVRM-KTCHN1,679,11-Sep-12:00 LIVRM-KTCHN1,613,11-Sep-12:10 BED-BATH-RM2,1173,11-Sep-12:10 LIVRM-KTCHN1,866,11-Sep-12:20 LIVRM-KTCHN1,354,11-Sep-12:30 LIVRM-KTCHN1,206,11-Sep-12:40 LIVRM-KTCHN1,318,11-Sep-12:50 BED-BATH-RM2,211,11-Sep-12:50 LIVRM-KTCHN1,240,11-Sep-13:00 LIVRM-KTCHN1,214,11-Sep-13:10 BED-BATH-RM2,504,11-Sep-13:10 LIVRM-KTCHN1,69,11-Sep-13:20 BED-BATH-RM2,333,11-Sep-13:20 LIVRM-KTCHN1,503,11-Sep-13:30 BED-BATH-RM2,1071,11-Sep-13:30 LIVRM-KTCHN1,32,11-Sep-13:40 LIVRM-KTCHN1,50,11-Sep-14:00 LIVRM-KTCHN1,363,11-Sep-14:10 BED-BATH-RM2,35,11-Sep-14:10 LIVRM-KTCHN1,450,11-Sep-14:20 BED-BATH-RM2,49,11-Sep-14:21 LIVRM-KTCHN1,201,11-Sep-14:30 LIVRM-KTCHN1,128,11-Sep-15:00 BED-BATH-RM2,41,11-Sep-15:00 LIVRM-KTCHN1,273,11-Sep-15:10 BED-BATH-RM2,125,11-Sep-15:10 LIVRM-KTCHN1,126,11-Sep-15:20 DOOR,8,11-Sep-15:29 LIVRM-KTCHN1,123,11-Sep-15:30 CAR3,430,11-Sep-15:41 CAR3,525,11-Sep-15:51 CAR3,646,11-Sep-16:01 CAR3,515,11-Sep-16:11 BED-BATH-RM2,21,11-Sep-18:20 DOOR,8,11-Sep-19:00 BED-BATH-RM2,18,11-Sep-19:00 LIVRM-KTCHN1,25,11-Sep-19:01 LIVRM-KTCHN1,432,11-Sep-19:10 BED-BATH-RM2,169,11-Sep-19:10 LIVRM-KTCHN1,371,11-Sep-19:20 LIVRM-KTCHN1,706,11-Sep-19:31 LIVRM-KTCHN1,213,11-Sep-19:40 LIVRM-KTCHN1,160,11-Sep-19:50 LIVRM-KTCHN1,860,11-Sep-20:00 LIVRM-KTCHN1,302,11-Sep-20:10 BED-BATH-RM2,92,11-Sep-20:10 LIVRM-KTCHN1,528,11-Sep-20:20 LIVRM-KTCHN1,1019,11-Sep-20:30 BED-BATH-RM2,403,11-Sep-20:30 LIVRM-KTCHN1,817,11-Sep-20:40 BED-BATH-RM2,1423,11-Sep-20:40 LIVRM-KTCHN1,898,11-Sep-20:50 BED-BATH-RM2,194,11-Sep-20:50 LIVRM-KTCHN1,290,11-Sep-21:00 LIVRM-KTCHN1,223,11-Sep-21:10 LIVRM-KTCHN1,465,11-Sep-21:20 LIVRM-KTCHN1,815,11-Sep-21:30 LIVRM-KTCHN1,498,11-Sep-21:40 LIVRM-KTCHN1,911,11-Sep-21:50 LIVRM-KTCHN1,510,11-Sep-22:00 BED-BATH-RM2,18,11-Sep-22:00 LIVRM-KTCHN1,585,11-Sep-22:10 BED-BATH-RM2,34,11-Sep-22:10 BED-BATH-RM2,42,11-Sep-22:20 LIVRM-KTCHN1,555,11-Sep-22:21 LIVRM-KTCHN1,509,11-Sep-22:30 LIVRM-KTCHN1,1119,11-Sep-22:40 LIVRM-KTCHN1,830,11-Sep-22:50 LIVRM-KTCHN1,699,11-Sep-23:00 LIVRM-KTCHN1,596,11-Sep-23:10 LIVRM-KTCHN1,1086,11-Sep-23:20 LIVRM-KTCHN1,743,11-Sep-23:30 LIVRM-KTCHN1,402,11-Sep-23:40 LIVRM-KTCHN1,704,11-Sep-23:50 LIVRM-KTCHN1,536,12-Sep-00:00 LIVRM-KTCHN1,399,12-Sep-00:10 BED-BATH-RM2,51,12-Sep-00:10 LIVRM-KTCHN1,587,12-Sep-00:20 LIVRM-KTCHN1,510,12-Sep-00:30 LIVRM-KTCHN1,370,12-Sep-00:40 LIVRM-KTCHN1,667,12-Sep-00:50 LIVRM-KTCHN1,582,12-Sep-01:00 BED-BATH-RM2,79,12-Sep-01:01 LIVRM-KTCHN1,652,12-Sep-01:10 BED-BATH-RM2,97,12-Sep-01:10 LIVRM-KTCHN1,365,12-Sep-01:20 LIVRM-KTCHN1,478,12-Sep-01:30 LIVRM-KTCHN1,317,12-Sep-01:40 LIVRM-KTCHN1,290,12-Sep-01:50 BED-BATH-RM2,68,12-Sep-01:50 LIVRM-KTCHN1,51,12-Sep-02:00 BED-BATH-RM2,125,12-Sep-02:00 BED-BATH-RM2,82,12-Sep-02:10 BED-BATH-RM2,54,12-Sep-02:20 BED-BATH-RM2,28,12-Sep-02:50 BED-BATH-RM2,33,12-Sep-03:00 BED-BATH-RM2,111,12-Sep-03:10 BED-BATH-RM2,26,12-Sep-03:30 BED-BATH-RM2,19,12-Sep-03:50 BED-BATH-RM2,24,12-Sep-04:00 BED-BATH-RM2,26,12-Sep-04:10 BED-BATH-RM2,41,12-Sep-04:50 BED-BATH-RM2,26,12-Sep-05:20 BED-BATH-RM2,114,12-Sep-05:40 BED-BATH-RM2,16,12-Sep-05:51 BED-BATH-RM2,48,12-Sep-06:00 BED-BATH-RM2,253,12-Sep-06:10 BED-BATH-RM2,40,12-Sep-06:20 BED-BATH-RM2,22,12-Sep-07:00 BED-BATH-RM2,45,12-Sep-07:10 BED-BATH-RM2,116,12-Sep-07:21 BED-BATH-RM2,25,12-Sep-07:30 LIVRM-KTCHN1,25,12-Sep-07:50 BED-BATH-RM2,137,12-Sep-07:51 LIVRM-KTCHN1,37,12-Sep-08:00 BED-BATH-RM2,124,12-Sep-08:00 BED-BATH-RM2,30,12-Sep-08:20 BED-BATH-RM2,31,12-Sep-08:30 BED-BATH-RM2,49,12-Sep-08:40 BED-BATH-RM2,27,12-Sep-08:50 LIVRM-KTCHN1,484,12-Sep-09:00 BED-BATH-RM2,171,12-Sep-09:01 LIVRM-KTCHN1,424,12-Sep-09:10 BED-BATH-RM2,55,12-Sep-09:10 LIVRM-KTCHN1,595,12-Sep-09:20 BED-BATH-RM2,61,12-Sep-09:20 LIVRM-KTCHN1,915,12-Sep-09:30 LIVRM-KTCHN1,623,12-Sep-09:40 LIVRM-KTCHN1,311,12-Sep-09:50 LIVRM-KTCHN1,283,12-Sep-10:00 LIVRM-KTCHN1,470,12-Sep-10:10 BED-BATH-RM2,16,12-Sep-10:10 LIVRM-KTCHN1,493,12-Sep-10:20 BED-BATH-RM2,54,12-Sep-10:21 LIVRM-KTCHN1,697,12-Sep-10:30 LIVRM-KTCHN1,703,12-Sep-10:40 LIVRM-KTCHN1,718,12-Sep-10:50 BED-BATH-RM2,255,12-Sep-10:50 LIVRM-KTCHN1,626,12-Sep-11:00 BED-BATH-RM2,539,12-Sep-11:00 BED-BATH-RM2,61,12-Sep-11:10 LIVRM-KTCHN1,179,12-Sep-11:11 LIVRM-KTCHN1,1002,12-Sep-11:20 BED-BATH-RM2,26,12-Sep-11:20 LIVRM-KTCHN1,362,12-Sep-11:30 BED-BATH-RM2,55,12-Sep-11:30 LIVRM-KTCHN1,364,12-Sep-11:40 LIVRM-KTCHN1,940,12-Sep-11:50 BED-BATH-RM2,27,12-Sep-11:51 LIVRM-KTCHN1,671,12-Sep-12:00 BED-BATH-RM2,99,12-Sep-12:00 LIVRM-KTCHN1,262,12-Sep-12:10 BED-BATH-RM2,27,12-Sep-12:10 LIVRM-KTCHN1,70,12-Sep-12:20 LIVRM-KTCHN1,449,12-Sep-12:30 LIVRM-KTCHN1,263,12-Sep-12:40 LIVRM-KTCHN1,992,12-Sep-12:50 BED-BATH-RM2,111,12-Sep-12:51 DOOR,8,12-Sep-12:53 LIVRM-KTCHN1,184,12-Sep-13:00 BED-BATH-RM2,26,12-Sep-13:00 DOOR,8,12-Sep-13:06 LIVRM-KTCHN1,89,12-Sep-13:10 DOOR,8,12-Sep-13:11 DOOR,8,12-Sep-13:16 LIVRM-KTCHN1,460,12-Sep-13:20 BED-BATH-RM2,82,12-Sep-13:20 BED-BATH-RM2,26,12-Sep-13:40 # Records exported: 389 Older records skipped: 6726