StreetProof™
Claim

Public evidence packet

Posti

ent_e2025e06135cbae5 · Lahti

Open JSONPresence Record
Physical citations
10
corroborated or strictly verified
Observed assets
1
6 coverage cells
Score status
Evidence building
10 accepted citations · stable score pending
Last observed
2026-11-03
first 2026-09-08
Experimental score details

Provisional PPS: 43. This early estimate is not a stable Presence Score or a public cohort rank. It can change sharply as independent evidence grows.

What this proves

  • An accepted physical citation records that a brand or asset was observed at a documented time and privacy-safe place.
  • The citation's presence_kind states whether it supports location_presence, mobile_presence, or brand_mention.

What this does not prove

  • Ownership or control of an observed location or asset.
  • Licensing, legal status, legitimacy, quality, reputation, or continued operation.
  • Endorsement, affiliation, or customer sentiment.
  • Audience size, impressions, reach, conversions, sales, revenue, or return on investment.
  • A complete asset inventory, exhaustive city coverage, or absence when no matching citation exists.
Citation formats

Use this packet in reports

Plain English

Posti has a StreetProof Presence Record for Lahti with 10 public corroborated or strictly verified observations across 1 observed asset.

Newsroom

Posti has a StreetProof Presence Record for Lahti with 10 public corroborated or strictly verified observations across 1 observed asset. Source: StreetProof, https://streetproof.com/entity/lahti/posti/evidence

JSON citation
{
  "source": "StreetProof",
  "record": "ent_e2025e06135cbae5",
  "name": "Posti",
  "public_observations": 10,
  "physical_citations": 10,
  "brand_mentions": 0,
  "local_operation_observed": false,
  "unique_assets": 1,
  "pps_current": null,
  "provisional_pps": 42.69,
  "score_state": "provisional",
  "evidence_url": "https://streetproof.com/entity/lahti/posti/evidence",
  "methodology_url": "https://streetproof.com/methodology"
}
Observation sample

Recent public ledger rows

Methodology
ObservedSourceAssetCitation typeCellStateLedger hash
2026-11-03reviewed_sensor_sourceast_ps_04654d1c5f3724b9 · vehicle_wrapmobile_presence891120c2e27ffffcorroboratedcc71c7834ecb590fdf294c8f39237bc1bf029dcbda8ae43bd3666adf71bb6bc3
2026-10-30reviewed_sensor_sourceast_ps_04654d1c5f3724b9 · vehicle_wrapmobile_presence891126a0923ffffcorroborated3c569ed976022868cec16a472e4a86994b98a22320e65bc35fca47d59174b0f6
2026-10-30reviewed_sensor_sourceast_ps_04654d1c5f3724b9 · vehicle_wrapmobile_presence891126a72bbffffcorroborated0e4087a596ea2fafdd22b1f3a8cea257836b421a0cf673b5a358b418399c43cb
2026-10-30reviewed_sensor_sourceast_ps_04654d1c5f3724b9 · vehicle_wrapmobile_presence89112634e97ffffcorroborated35bd4733c71270e6fec9ce460535db44f0d25559af902bcb82c2c7d57009f53a
2026-10-13reviewed_sensor_sourceast_ps_04654d1c5f3724b9 · vehicle_wrapmobile_presence891126a0977ffffcorroborated7bc16b859b155c96f8650ba03a65d60eb03e010c923ac0c64a83445fa6e1d907
2026-09-22reviewed_sensor_sourceast_ps_04654d1c5f3724b9 · vehicle_wrapmobile_presence891126a502fffffcorroborated578fb032ad632d369b2c0047bcbc966b5f1e8b160c4e323c05497c2d6adfa06a
2026-09-14reviewed_sensor_sourceast_ps_04654d1c5f3724b9 · vehicle_wrapmobile_presence891126a502fffffcorroborated598e4aa5ef0deafe04af9c0a72f0a5026ce9a9ba689cb5c7cdc2f28a95d8d7a4
2026-09-10reviewed_sensor_sourceast_ps_04654d1c5f3724b9 · vehicle_wrapmobile_presence891126a502fffffcorroboratedba6b3877b9eceafbb5087a00cfb70efc1994190ee8a03d9f08133cc470bc4402
2026-09-08reviewed_sensor_sourceast_ps_04654d1c5f3724b9 · vehicle_wrapmobile_presence891126a502fffffcorroborated322977deb3e733adb6891df4fbedf7a22e3954139a43b0518e96e1d7728e21ab
2026-09-08reviewed_sensor_sourceast_ps_04654d1c5f3724b9 · vehicle_wrapmobile_presence891120c2e27ffffcorroboratedee995d9d296f38cdf30d30a186dfa1330df98cf28734f4b2a4e9cfccfee8957d

Source mix

reviewed_sensor_source
10

Verification mix

corroborated
10

Physical citation mix

mobile_presence
10

This page is the public citation packet. The owner proof pack remains separate because it includes business-facing machine-read and claim context. Use the JSON packet for agents, reports, and partner diligence.