Robinhood Stock Popularity History
1 year of hourly data of the number of Robinhood users that own each stock
@kaggle.cprimozi_robinhood_stock_popularity_history
1 year of hourly data of the number of Robinhood users that own each stock
@kaggle.cprimozi_robinhood_stock_popularity_history
This data set consists of >1 year of historical data about the number of users that hold each stock available on the Robinhood stock brokerage. It is the dataset that powers https://robintrack.net/
Data was collected from the Robinhood API once per hour over the entire period.
The popularity metric represents the number of unique accounts that hold at least one share of the asset. This only includes normal, long shares (not options).
Robinhood provides their popularity data publicly, which I feel is a great step in the right direction for an industry (finance) where data has traditionally been expensive, low-quality, and hard to find. I feel it's only right that I share this historical popularity data freely as well.
Robinhood gives free shares of a certain set of stocks as rewards to users for referring others to their platform. Some of the most popular stocks are at the top because of this.
The popularity metrics change over weekends and when the market is closed due to the fact that Robinhood accounts can be created/closed/transferred over those periods. The metric reported at each timestamp is the exact value that the Robinhood API reported at that instant.
This data can be used as a measure of retail sentiment. By seeing what traders do in response to changes in price and different news events, it can be determined if retail traders are "buying the dip" or panicking and leaving the market.
I didn't include price data due to possible legal limitations. However, it should be relatively easy to obtain this data yourself from a different source and combine it with this data set.
CREATE TABLE djpy (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dk (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dkily (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dkl (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dks (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dl (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dla (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dlaky (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dlb (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dlbr (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dlbs (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dlhc (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dln (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dlng (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dlph (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dlpn (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dlr (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dls (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dlth (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dltr (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dlx (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dm (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dmac (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dmb (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);CREATE TABLE dmdv (
"timestamp" TIMESTAMP,
"users_holding" BIGINT
);Anyone who has the link will be able to view this.