2Timer
← Back to 2Timer

2Timer Help

Practical guides for humans, with structure that is easy for AI systems to parse.

Importing Data

Purpose

Load external participant and meet data with predictable field mapping and fewer race-day surprises.

Prerequisites

  • An existing meet in 2Timer (create one via New Meet on the home screen).
  • Source file exported from your registration or meet software.
  • A bib assignment strategy confirmed before import — bib number is the primary matching key for most operations.

Supported Import Sources

Go to Import inside your meet to see all available importers.

CSV Participant Import

Used for participant lists from any source that can produce a spreadsheet export.

  • Detects comma, tab, semicolon, and pipe delimiters automatically.
  • Presents a column mapping UI to match source columns to 2Timer fields (name, bib, gender, age, event, team, city, etc.).
  • Required minimum: a bib number or a name (ideally both).
  • If an event column is present, athletes are automatically linked to the matching event number.

Tips:

  • Export from your registration platform as CSV before the meet. RunSignUp, RaceSignUp, ACTIVE, and most platforms support CSV download.
  • TFRRS roster exports are supported in this importer. TFRRS ID maps into 2Timer’s external athlete ID field, and season columns like 2023 Outdoor map to athlete grade.
  • If your file has no headers, assign columns manually in the mapping step.
  • Re-importing with the same bibs updates existing records rather than creating duplicates.
  • If your file includes team codes but you have not created teams yet, import first and then review Teams so display names are clean.

TFRRS Results Export

Used to export track and field meet results in the no-header CSV layout accepted by TFRRS.

  • Available from Export → Results → TFRRS.
  • Writes one row per exportable result with TFRRS-style base columns, relay-athlete slots, and field-attempt columns.
  • Uses the athlete registration_id field as the outbound TFRRS ID when present.

Hytek Semicolon Entries Import

Used for .txt or .hy3 files in the common semicolon-delimited meet-data format. This format is often associated with HY-TEK, but many platforms can export it.

  • Parses the standard semicolon entry format including athlete name, team, division, event, and entry/seed mark.
  • Track & field and cross country entry files are both supported.
  • Event numbers in the source file must match event numbers in your 2Timer meet. Create the events first if needed.

This is not the same as Hytek .TCL fixed-width files.

Tips:

  • If you are exporting from HY-TEK, use File → Export → Entries and choose the semicolon-delimited format.
  • Relay entries include team code and leg information.
  • Entry marks are imported into the entry seed slot for seeding and start lists. They are not imported as finished results.
  • Hytek prior-round finish place advancer fields are not treated as final result places during entry import.
  • Team records can also be imported separately if you want full school names, not just codes.

Hytek TCL Roster Import

Used for fixed-width Hytek .tcl or .txt files exported by Hytek Meet Manager or Team Manager.

  • Imports teams and athletes only in v1.
  • Reads roster-style files and mixed results/advancer files by extracting the stable team and athlete records.
  • Does not import events, entries, relay lineups, or results from TCL files in v1.
  • Runs as a single in-meet import flow rather than separate team and athlete screens.
  • Shows one preview with:
    • new teams to add
    • new athletes to create
    • existing athletes that can be safely backfilled
    • conflicts that will be skipped

Tips:

  • From the meet dashboard, choose Import → Hytek TCL.
  • Use this when your source file is a fixed-width .TCL export rather than a semicolon file.
  • If you are creating a brand-new meet from Hytek event data, use the semicolon workflow instead.
  • Mixed results-style TCL files can still be useful here because they usually include team and athlete rows even when result rows are present.
  • If your real goal is to import entries, not roster data, the semicolon importer is still the supported option today.

RunSignUp Sync

For road races registered on RunSignUp, the RunSignUp connector provides a live sync of participant data without manual file exports.

  1. In app Settings → Integrations, connect your RunSignUp account via OAuth.
  2. In your meet, add a RunSignUp connector under Connectors and associate it with the correct race and event.
  3. Use the connector’s Sync control to pull the latest participant list on demand.

See Connectors for full setup.

FinishLynx Results Import

Used to import result times from FinishLynx LIF (Lynx Interface File) files.

  • LIF files contain track results with chip ID, bib, name, time, place, and reaction time.
  • Imported as raw reads that are then processed against your markers and entries.

FinishLynx athlete and team files can also be imported through the Lynx import paths when you are using Lynx as a roster source rather than only a results source.

This import happens automatically when a FinishLynx connector is active and watching a folder. See Connectors.

FieldLynx Results Import

Used to import field-event results from LFF (Lynx Field File) files.

  • LFF files contain field event marks, attempts, and optional wind data.
  • Imported through the FinishLynx connector’s shared Lynx folder workflow.

RTQL / Manual Results Import

Used to paste or upload a timing system’s results string directly when no automated connector is available.

2Timer Archive Import

Used to restore a previously exported .2t meet file on a different machine or browser.

  1. From the home screen, click Import Meet.
  2. Select the .2t archive file.
  3. The meet restores with all athletes, entries, and results intact.

Common Issues

Problem Likely Cause Fix
Header mismatch Column names don’t match expected format Use the manual column mapping step
Duplicate bibs Same bib appears in source twice Correct upstream data and re-import
Unknown event reference Event number in file not found in meet Create the event first, then re-import
Athlete linked to wrong event Event column misread Verify delimiter and event column mapping
Missing athletes after import Below-minimum required fields Confirm at least bib or name is present

Verification Checklist

  • Athlete count matches your registration system’s total.
  • Bib numbers are unique across the meet (or per event, as intended).
  • Entries are assigned to the expected events.
  • Seed times and field marks appear in the seed column, not the finish/result column.
  • Teams and affiliations are assigned for scored cross country meets.

Related Pages

Metadata

  • Last Updated: 2026-04-12
  • Version: 0.5
  • Status: Active