> For the complete documentation index, see [llms.txt](https://docs.wiclax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wiclax.com/en/other-features/export-variables.md). # Export variables Here is a complete reference for cases when you'll need to enter them in a raw fashion ## Variables for a participant

ID	Data
21	Bib number
3	First name
2	Last name
4	Full name
68	Full name, initials for first name
8	Gender
5	Category - abbreviation
52	Category - full name
7	Team or Club
24	Team code
10	Birth year
37	Birth date
49	Age
12	Address line 1
13	Address lin 2
17	Zip code
18	Town
72	State or Province
14	Region
9	Nationality
61	Country name
16	Email
43	Phone number
15	License number
19	Race
39	Chip ID
60	Real bib number or Car number
1	UCI ID
82	Heat number
76	List of teammate names (when teams exported)

## Result variables

ID	Data
22	Race time
23	Start time, individual
98	Scheduled start time, individual
80	Race start time
40	Chip time (vs Gun time)
74	Gun time (vs Chip time)
30	Rank
31	Rank in category
75	Rank in gender
88	Rank at general classification
47	Number of laps
83	Number of remaining laps
58	Best lap
34	Time diff to race leader
108	Time diff to predecessor
66	Time diff at general classification
29	Average speed
85	Points
28	Race distance
45	Time of day - for finish
48	Total distance completed
91	Race time at last split timed
92	Rank at last split timed
93	Name of last split point timed
55	List of split times (format "`time_split1 (rank)\|time_split2 (rank)\|...`")
56	List of segment times (format "`time_segment1 (rank)\|time_segment2 (rank)\|...`")
89	List of lap times (format "`time_lap1\|time_lap2\|...`")
96	Lap average speed
81	Number of participants in the race (excl. non starters)
77	Number of participants in the gender (excl. non starters)
78	Number of participants in the category (excl. non starters)
94	Number of finishers in the category
38	Number of finishers in the race
200,201,202, ...	Net split time for first, second, ... split point. Numbering valid for all the event splits
300, 301, 302, ...	Segment time for first, second, ... segment. Numbering valid for all the event segments
400, 401, 402, ...	Time of day for first, second, ... split point. Numbering valid for all the event splits
500, 501, 502, ...	Rank for first, second, ... split point. Numbering valid for all the event splits
600, 601, 602, ...	Rank for first, second, ... segment. Numbering valid for all the event segments

## Custom data fields

ID	Data
xxx	Where xxx is simply the name of the custom data in the Wiclax event. For example `[%Dog name%]`. Case insensitive.

## Race variables

ID	Data
9013	Event name
9017	Event organizer
9000	Race title
9014	Report title
9001	Number of starters
9002	Number of ranked
9025	Number of finishers
9022	Winner race time
9003	Winner average speed
9004	Event date
9005	Race commissaires
9006	Race distance
9007	Stage name
9057	Stage number
9024	Race start time
9008	Best lap
9018	Best lap holder, full name
9019	Best lap holder, last name
9020	Best lap holder, full name with initials
9023	Number of laps to complete
9011	Number of laps completed
9012	Number of laps remaining
9021	Total number of laps completed (all participants)
9015	Number of DNF participants
9016	Number of OTF participants (out of time limit)
9059	List of all split points, comma separated
9060	List of all segments, comma separated
xxx	Where xxx is simply the name of a custom variable in the Wiclax event. For example `[%Water temperature%]`. Case insensitive.

## Stage or Lap specifiers For multi-stage events, the stage index used for a variable is by default the stage of the export. A variable ID - or tag - can be completed by a specifier to ensure the variable is calculated for a specific stage number or a specific lap number. Both indexes start at 1. Examples:

ID	Data
[%23,stage=2%]	Gives the participant start time (23) for stage 2
[%600,lap=1%]	Gives the participant's 1st segment time for lap 1

## Teammate variables Variable tags can be formed around variable #2000, which indicates you want a participant data for a specific teammate, when the export is itself a team ranking or a team list. The tag format is as follows: `2000,,,` Where team-sorting value can be `reg` for the order of registration or `res` for the ranking order. Teammate index starting at 0. Example:

ID	Data
[%2000,0,3,res%]	Gives the first-name (var 3) of the 1st ranked teammate

## Variable formatting For specific contexts like exporters or scoreboards, some format flags can be specified in this way: ``` [%var=30;fixedW=3;maxW=3;align=right;trailing=.%] ``` In this case the whole block has to start with `var=`, followed by the variable ID and then a list of format specifiers separated by a semicolon. Here is the list of specifiers allowed:


fixedW	a fixed number of chars for the field, value is completed with padding chars if necessary
maxW	a maximum number of chars for the field, value is truncated if necessary
paddingChar	a character to use for padding when necessary, space by default
align	alignment for the value when fixedW is set, value left, right or center (left by default)
trailing	a suffix string to append when the value is not empty
leading	a prefix string to insert before the value when the value is not empty
timeFormat	a mask for time values, following reference https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings

## Special characters Also specific to exporters/scoreboards. To output any (non printable) special character based on its ASCII code, insert it like this: ``` {char:xx} ``` Where *xx* is the code. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.wiclax.com/en/other-features/export-variables.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.