Discover
Read configured RSS feeds and source pages.
Methodology & limitations
A record, not a prediction.
NATracker organizes published reporting about security incidents in Nigeria. It is designed for research and awareness, not real-time safety decisions.
How a report becomes a record
Read
Extract available article text and source metadata.
Qualify
Require a date and state; use exact town/LGA when known or disclosed surrounding-area/state precision when not.
Reconcile
Compare incident fingerprints to reduce duplication.
Publish
Show reporting status, location precision, casualty precision and source evidence with each record.
Evidence labels
Two or more cited sources, or an official statement plus a cited publisher.
Credible reporting exists, but important details or outcomes may still change.
A single source or incomplete corroboration; use with additional caution.
What each record contains
Known limitations
Coverage is incomplete
Source availability, redirects, rate limits and missing local reporting create gaps.
Dates and places can conflict
Publication date is never treated as the incident date without supporting information.
Numbers can be exact or approximate
Figures may change. Ranges and estimates are displayed as such; unknown is reserved for reports that identify an impact without a reliable figure.
Post-April counts are not a trend
Lower stored counts after April can reflect earlier strict date, location and casualty rules rather than fewer incidents.
Automation has limits
Source discovery can miss events or confuse related stories. Publication is not a reliability percentage.
Every record retains its supplied sources and timestamps. When a source is corrected or a report changes, figures should be reviewed against the cited source before the record is updated.