After two months of Eve downtime to move across the country to start a new job, I wanted to report on how Capital sales have been performing as Raath has been leading the construction of capitals hulls in my absence.
Looking at sales from 2012-06 to 2013-11, we are faced with shrinking margins on Carriers. With 139 data points covering over a year of sales, I think it is fairly easy to justify a trend from the data. The highest demand we saw was when TEST was defending Fountain, as the Slowcat doctrine was a training goal for a lot of pilots.
We have a much smaller dataset to work with for Dreadnoughts as the BPOs and workflow for incorporating them into the production line was a fairly recent addition. With only six months of sales data, it is hard to draw a strong conclusion but the margins look to be holding stronger than Carriers. I attribute a lot of our strong numbers holding Dreadnoughts up primarily due to the Naglfar rebalance in the Odyssey expansion; their profit margins are holding up around 40% on average due to demand, and plus it is cool vertical hull.
Note: we are not building the Phoenix hull due to general terribleness.
Let there be Database Rows
The only edits that I had to make to the project code were the database connection details in scraper.ini and a narrowing down of ship classes listed in toaster_shiplist.json. After getting the data into mySQL and importing the invTypes and mapSolarSystems tables from the static dump into my database, I could start to filter and sort the results.
Kicking off the scraper:
pi@charon ~/eve_prosper $ python zkb_scraper.py — startdate=2013-12-01DB Connection: GOODzKillboard connection: GOODno crash log found. Executing as normal…Parsed Capital Industrial Ship: [200, 29713239, 0, '2013-04-08'] sleep=20.0Parsed Capital Industrial Ship: [290, 27468307, 1, '2012-12-30'] sleep=20.0
Here is the query to get Racial JFs and also include the solar system name and security value:
– Get Racial JFs
SELECT destruction_data.date, destruction_data.week, destruction_data.typeID, destruction_data.systemID, destruction_data.destroyed, invTypes.typeName, mapSolarSystems.solarSystemName, mapSolarSystems.security
ON (destruction_data.typeID = invTypes.typeID)
ON (destruction_data.systemID = mapSolarSystems.solarsystemID)
WHERE destruction_data.typeID IN (28850, 28844, 28848, 28846)
ORDER BY destruction_data.date DESC
Out of 975 Jump Freighter kills covering 334 days, there is an average of 20 a week killed. It turns out that you are most likely to get caught in Lowsec in a Rhea.
When we look at kills by system, Purjola (0.5), a Highsec system in the Forge stands out as the system with the most losses at 54. Not surprisingly the Lowsec system of Sagain (0.4) comes in second, most likely due to the terrible kickout station that I have covered here.
More coming soon as I start to think of what types of statistics and trends I can pull out of the data. If you have something you would like me to look at, please leave a comment or tweet @K162space.
It has been a while since I have posted and that is because I have relocated from the US Midwest to California to pursue my dream of working as an engineer in the telecom industry.
My desktop hasn’t been moved because I haven’t found a permanent apartment to call home yet. I’ve only been able to update skill training with an old laptop that can barely run the client. Once things fall into place, I’ll get back into the swing of things.
A Tech 3 ship is a great example of an item that has high cross-selling opportunities. A Tech 3 hull by itself it useless; a person must assemble it by combining it with five Subsystem components –defensive, electronic, engineering, offensive, and propulsion. This requirement for flying the ship gives a trader the ability to also stock the necessary Subsystems and increase potential profits.
Tengu Hull Performance
I have found the Tengu hull to have the most volume out of the four racial Tech 3 hulls due to it’s PVP and PVE applications. The Loki hull is a close second, but it out-shined by the demand of the Tengu.
Over 473 days of trading I’ve sold 56 Tengu hulls. Moving 14.7 B ISK, I was able to achieve a 2.29 B total profit with the average profit per hull coming in at 41.65 M.
Tengu Subsystem Performance
The real trading power comes from using some intelligence and trending to find the most popular Subsystems. My analysis shows that the Amplification Node was the most profitable and also had the highest average profit. The Fuel Catalyst is also a strong performer as it had the second highest average profit. At the bottom of the list was the Covert Reconfiguration as I accredit the cloakey role to be a very niche role.
25 of the Tengu hull sales included the same client buying one or more Subsystems at or around the same time. On average a person bought 2.6 Subsystems with an average total of 52.4 M profit.
Further analysis shows that the best performance comes from also selling a person 3-4 Subsystems when they are also buying the Tengu hull as the average profit per Subsystem for these transactions types comes in at 21.7-22 M.
Lockefox got me thinking about my instincts for trading HACs a few days ago. I have always felt the Ishtar’s price to be historically less volatile than then Zealot so I went out to run the numbers and prove my theory.
P = time period
The numbers show that I was correct. If you want something stable to trade, go with the Vagabond. Higher risk items include the Ishtar and Zealot hulls.
Here is a snapshot of the historical buy prices for reference.
No, I am not leaving Eve. I have accepted an Engineering job in the San Francisco Bay Area and will be moving at the end of the summer. This is a major career advancement where I am going from a generalist to an Engineering specialist. My posting will become erratic, but I will return after I get the family settled from the cross-country move.
It is with great pain that I have to announce that my wallet manager code was compromised at an unknown time in the past. I haven’t spent too much time doing computer forensics because I believe that I was compromised on a previous VM that hosted my site in 2011, which has since been deleted in favor of a OS refresh.
Details about the compromise can be found on this stackoverflow.com post. If you have downloaded and are running a copy of my Wallet Manager, you will want to look at files in the /protected/models/ directory for the exploit code.
Going forward I am going to publish the Wallet Manager code to a public GitHub repository. My goal will be to secure the code, make it open source, and enable community contributions.