- Forums
-
Pricing
- Community Pricing
- Pricegrid
- Spreadsheet
- Browse Suggestions
- Latest Changes
- Unusual Pricelist
- Browse by Item
- Browse by Effect
- Steam Community Market
- Market Pricelist
-
Trading
- Classifieds
- Classified Listings
- Utilities
- Calculator
- Premium Search
- Statistics
I like Mornings
Thx Joxu
Sale 1)
https://backpack.tf/profiles/76561198310610808#!/compare/1480636800/1480723200
Sold for Kill-A-Watt Tough Stuff Muffs + 12 (ish) Keys in sweet
= 52
Sale 2)
https://backpack.tf/profiles/76561198077739824#!/compare/1477612800/1477699200
Sold for Blizzardy Storm Ketche + 33 Keys
Ketche = 11
= 44
Sale 3)
https://backpack.tf/profiles/76561198077739824#!/compare/1478304000/1478390400
Sold for Cloud 9 Master's Yellow Belt + 3 Keys in sweets
C9MYB -
https://backpack.tf/item/1796303004 - 1 Month Unsold @ 61
Taking 60 Keys
Seller atm @ 45 keys
https://backpack.tf/item/4935541989
Sales we have are:
52, 44 and 60
Going with 44-60
Thanks =)
that sale 2 is obviously a quicksell, lowtier unu + keys = basically pure
It took 8 days to sell: http://www.tf2outpost.com/trade/28552262
And that trade was reposted from http://www.tf2outpost.com/trade/28558099
EDIT: IM RETARDED
Yeah, the trade was reposted multiple times but it doesn't matter as the B/O stayed the same.
"It took 8 days to sell" if it was reposted from another trade, then it took longer than 8 days. That was my point :D
EDIT: IM RETARDED
The trade I linked was older though? I intentionally listed the oldest trade.
Nobody saw anything then cough
XD
44 has to be included as the seller @ 45 would counter 52-60
Only Logical sense
It seems like C9 Belt for 60 keys seems a bit off. :/
I haven't been suggesting for quite a long time, but I would've ignored that sale and just do 44-52 because the sale at 44 keys is practically pure and the sale at 52 keys is just considering when a sale isn't pure.
I don't know, but a mini-suggestion on c9 belt would definitely help. :)
http://www.tf2outpost.com/trade/28574860 - 50 key B/O caps sale #3
Thanks. Resolves the issue pointed out by Roller above.