> For the complete documentation index, see [llms.txt](https://docs.dunkest.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dunkest.com/fantasy-rules/late-registration.md).

# Late Registration

It is possible to register even **after the championship has already begun**.

### **Entry Score**

At the end of the Matchday in which you register, you will receive a score equal to the **average points earned by all teams registered up to that moment**.

### **Initial Budget**

Your budget will be: 95 **credits + 0.3 credits for each Matchday already played**.\
\&#xNAN;*Example:* you register in Matchday 7 → 95 + (0.3 × 6) = **96,8 credits**

### **Registering During a Matchday**

* You can buy the players that are still available.
* Your team’s score will **still be the average score**.
* Value variations will be active, but your **budget will remain unchanged**.


---

# 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.dunkest.com/fantasy-rules/late-registration.md?ask=<question>&goal=<endgoal>
```

`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.