> For the complete documentation index, see [llms.txt](https://docs.velogicfit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velogicfit.com/zh/di-02-jie-shi-yong-velogic-studio/triathlon-metrics.md).

# 铁人三项指标

Velogic Studio 中针对铁人三项和计时赛自行车姿势的专用身体角度范围和拟合流程指南。

虽然铁三/计时赛的绝大多数指标与公路车 fitting 相同，但还是有一些关键差异。

![](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-4e66de9c88e9ecbe801abdf9ae92cd160c0ea035%2Ftriathlon-position.png?alt=media) *铁人三项姿势*

身体角度的主要变化是躯干角度比公路车姿势低得多（这得益于将坐垫前移）。

## 身体角度范围

| 指标    | 范围                       |
| ----- | ------------------------ |
| 踝关节角度 | 平均100-120，范围 < 30        |
| 膝关节角度 | 最大140-145，最小 >68         |
| 髋关节角度 | 最大85-105；如果骑手有问题，可到120   |
| 肩部角度  | 平均75-100                 |
| 前臂角度  | 平均0-20（5-10是一个不错的起点）     |
| 躯干角度  | 精英级10-15，普通20-30，30以上较少见 |

关节活动目标与公路姿势相同：

## 关节活动目标

| 指标     | 平均范围 | 良好范围 |
| ------ | ---- | ---- |
| 膝盖横向移动 | <40  | <20  |
| 膝盖移动角度 | <8   | 0-2  |
| 髋部垂直移动 | <40  | <15  |
| 髋部水平移动 | <40  | <10  |
| 踝部摆动   | <10  | \~5  |
| 肩部横向移动 | <40  | \~20 |

## 铁三/计时赛专用指标

| 指标     | 范围（铁三/计时赛） |
| ------ | ---------- |
| 膝盖在脚上方 | 20到80      |
| 坐姿角    | 78到86      |

关节对齐才是我们真正能看到将坐垫前移所带来影响的地方。作为起点，目标设为80度的坐姿角，然后以此为基础，在骑手舒适度与够到把位的能力之间取得平衡。如果受到 UCI 规则限制，你就需要尝试使用截短坐垫，以达到正确的坐姿角。如果你同时为骑手做公路车和铁三/计时赛车的 fitting，那么在公路下把位和铁三休息把位下的髋角及相关指标应当相当接近。

## 铁三/计时赛 fitting 流程

铁三/计时赛 fitting 的流程（大致）是：

1. 调整坐垫前后位置，使其坐姿角处于正确范围
2. 微调坐垫高度，以尽量减少髋/膝动作，并达到正确的膝/踝角度
3. 调整扶手垫的前伸量，使其尽量位于肩膀正下方，并将肩部横向移动降到最低
4. 调整到变速器的前伸量，使骑手的肘部能放在垫上，同时双手能轻松触及变速器。
5. 根据髋/膝动作、髋角以及骑手反馈来设置落差
6. 反复调整所需步骤，直到达到稳定、舒适的姿势

## 需要问骑手的问题

1. 颈部疼痛？
2. 肘部承重？
3. 坐垫鼻头压力？
4. 肩外侧疼痛？

## 其他需要留意的问题

1. 骑手为够到把手而伸展肩部（肩胛下沉），而不是降低躯干（把位太低）
2. 骑手在坐垫上频繁移动（坐垫不合适、把位太低或太长）

注意，短曲柄臂可以通过增大最小膝角和髋角，显著提升空气动力姿势的可持续性。


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.velogicfit.com/zh/di-02-jie-shi-yong-velogic-studio/triathlon-metrics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.