OFFSET and SOFFSET clauses

Use OFFSET to specify the number of rows to skip in each InfluxQL group before returning results. Use SOFFSET to specify the number of series to skip before returning results.

OFFSET clause

The OFFSET clause skips N rows in each InfluxQL group before returning results. Offsets honor row limits specified in the LIMIT clause and display the limited number of rows after the specified offset. Use LIMIT and OFFSET together to paginate query results.


SELECT_clause FROM_clause [WHERE_clause] [GROUP_BY_clause] [ORDER_BY_clause] [LIMIT_clause] OFFSET N [SLIMIT_clause] [SOFFSET_clause]


  • N: Number of rows to skip in each InfluxQL group before returning results.

Notable OFFSET clause behaviors

  • If there is no LIMIT clause in a query with an OFFSET clause, the query returns a single row per InfluxQL group at the specified offset.
  • If the query doesn’t include a GROUP BY clause, the entire result set is considered a single group and is returned in full.
  • If a query groups data by time, the offset is applied after aggregate and selector operations are applied to each time window.
  • If the WHERE clause includes a time range and the OFFSET clause causes InfluxQL to return points with timestamps outside of that time range, InfluxQL returns no results.


The following examples use the Get started home sensor sample data.

Return the nth row

Paginate results by 3 and return the 2nd page of results

Paginate results from each series by 3 and return the 2nd page of each series

SOFFSET clause

InfluxQL is being rearchitected to work with the InfluxDB 3.0 storage engine. This process is ongoing and some InfluxQL features, such as SOFFSET are still being implemented. For more information, see InfluxQL feature support.

Was this page helpful?

Thank you for your feedback!

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

InfluxDB Cloud Serverless