All scores are claimed scores unless otherwise noted.January: CWOps CWT 1300Z January 3•QSOs: 53•Mults: 52•Score: 2,756•Op Time: 30 minutesSession 1 for 2018. Still on my program to avoid cluster spots, call history etc. to minimize the use of operating crutches and force me to copy 100% of what is sentJanuary: CWOps CWT 1900Z January 3•QSOs: 13•Mults: 13•Score: 169•Op Time: 10 minutesSession 2 for 2018January: CWOps CWT 300Z January 4•QSOs: 37•Mults: 36•Score: 1,332•Op Time: 20 minutesSession 3 for 2018. One of the very rare days when I operated all 3 CWTs.January: ARRL RTTY Roundup (Final Score) •QSOs: 1,071•Mults: 98•Score: 103,684•Op Time: 20:45Eighth place for US/VE SOLP, third place Central Division, first place Indiana. My highest QSO total ever in any contest, and a higher score than last year's Round Up. More QSO's, more mults, what's not to like about how I spent the weekend? My biggest improvement was in the number of DX multipliers. I tracked my score on line and prefer the format used by contestonlinescore.com as they separate the assisted and the unassisted categories. I operated unassisted but, looking at the early returns on 3830, it seems like I might have placed higher overall had I operated with assistance as the scores in that category seem to be smaller. One of the things I like about the Round Up is you don't have to have big antennas to post a big score as there is nothing gained by running Europeans one after the other as is the case with CQWW, for instance. Mults count once, not once per band, and all QSOs count for the same point total regardless of where the station is located. So after you work that first station from France and that first station from Indiana, thereafter you can tune right past all the weaker French stations and work the louder Indiana stations first. January: NAQP CW•QSOs: 921•Mults: 196•Score: 180,516•Op Time: 12 hoursDecided to operate in the M2 category to give me the benefit of using spotting and being able to operate the entire 12 hours. Unfortunately I did not fully understand the 10-minute band change rule, so had to submit my log as a check log.January: CWOps CWT 1300Z January 10•QSOs: 66•Mults: 66•Score: 4,356•Op Time: 45 minutesSession 4 for 2018.January: CWOps CWT 1900Z January 10•QSOs: 90•Mults: 86•Score: 7,740•Op Time: 60 minutesSession 5 for 2018.January: CWOps CWT 1300Z January 17•QSOs: 63•Mults: 63•Score: 3,969•Op Time: 38 minutesSession 6 for 2018. January: CWOps CWT 1900Z January 17•QSOs: 52•Mults: 42•Score: 2,704•Op Time: 30 minutesSession 7 for 2018.January: NAQP SSB•QSOs: 192•Mults: 84•Score: 16,128•Op Time: 5 hoursVery little high band or low band activity, so almost all QSO’s were on 20M and 40M.January: CWOps CWT 1300Z January 24•QSOs: 49•Mults: 43•Score: 2,107•Op Time: 30 minutesSession 8 for 2018.January: CWOps CWT 0300Z January 25•QSOs: 58•Mults: 54•Score: 3,132•Op Time: .75 minutesSession 9 for 2018.January: CQ 160•QSOs: 441•Points: 1,032•Mults: 63•Score: 65,016•Op Time: 7.5 hoursThe bands were quiet and activity was high, always a good recipe for fun. All QSOs were made on the long wire.January: ARRL DX CW•QSOs: 60•Points: 174•Mults: 46•Score: 8,004Not a serious effort but did manage to work Palau for a new band slot on 40M.February: CWOps CWT 1300Z February 21•QSOs: 60•Mults: 59•Score: 3,540•Op Time: 30 minutesSession 10 for 2018. February: CWOps CWT 1300Z February 21•QSOs: 83•Mults: 81•Score: 6,723•Op Time: 60 minutesSession 11 for 2018. February: CWOps CWT 300Z February 22•QSOs: 33•Mults: 33•Score: 1,089•Op Time: 20 minutesSession 12 for 2018. Another rare day when I operated in all 3 CWTs.February: NAQP RTTY•QSOs: 618•Mults: 116•Score: 71,688•Op Time: 10 hoursVery strange band conditions at the start. Nothing on 15M or 10M so no mults to be had there. Some stations heard on 20M but they were often east and west coasters working each other and they could not hear me. So, went to 40M and 80M much earlier than usual. Pretty good performance in terms of total QSOs but could not make up for the lack of mults, so my overall score was a disappointment.February: CWOps CWT 1300Z February 28•QSOs: 53•Mults: 53•Score: 2,809•Op Time: 30 minutesSession 13 for 2018. February: CWOps CWT 1900Z February 28•QSOs: 41•Mults: 41•Score: 1,681•Op Time: 30 minutesSession 14 for 2018. March: CWOps CWT 1300Z March 7•QSOs: 121•Mults: 100•Score: 12,100•Op Time: 1 hourSession 15 for 2018. My best score of the year. In fact, the best in a long time.March: CWOps CWT 1900Z March 7•QSOs: 39•Mults: 39•Score: 1,521•Op Time: 30 minutesSession 16 for 2018. March: WIQP•QSOs: 81•Points: 159•Mults: 43•Score: 6,837A modest effort compared to previous years.March: CWOps CWT 1300Z March 14•QSOs: 97•Mults: 91•Score: 8,827•Op Time: 1 hourSession 17 for 2018. Signed as K9WX/m to test the log integration issues with DXLab and the /m callsign, but operated from the shack.March: CWOps CWT 1900Z March 14•QSOs: 31•Mults: 31•Score: 961Op Time: 30 minutesSession 18 for 2018. March: CWOps CWT 1300Z March 21•QSOs: 81•Mults: 77•Score: 6,237•Op Time: 45 minutesSession 19 for 2018.March: CWOps CWT 1900Z March 21•QSOs: 30•Mults: 30•Score: 900Op Time: 30 minutesSession 20 for 2018.March: CWOps CWT 1300Z March 28•QSOs: 26•Mults: 26•Score: 900Op Time: 20 minutesSession 21 for 2018. Signed as K9WX/m but operated from shack.March: CWOps CWT 1900Z March 28•QSOs: 79•Mults: 74•Score: 5,846Op Time: 60 minutesSession 22 for 2018.April: CWOps CWT 1300Z April 18•QSOs: 45•Mults: 44•Score: 1,980Op Time: 30 minutesSession 23 for 2018.April: CWOps CWT 1300Z April 25•QSOs: 30•Mults: 30•Score: 900Op Time: 30 minutesSession 24 for 2018. Signed as K9WX/mApril: CWOps CWT 1900Z April 25•QSOs: 22•Mults: 21•Score: 462Op Time: 30 minutesSession 25 for 2018. Signed as K9WX/m and operated from driveway to test INQP mobile setup.April: FQP•QSOs: 11•Points: 44•Mults: 11•Score: 484Op Time: a few minutesMay: CWOps CWT 1300Z May 02•QSOs: 32•Mults: 32•Score: 1,024Op Time: 30 minutesSession 26 for 2018. Signed as K9WX/m and operated from driveway to test INQP mobile setup.May: CWOps CWT 1900Z May 02•QSOs: 33•Mults: 31•Score: 1,023Op Time: 30 minutesSession 27 for 2018. Signed as K9WX/m and operated from driveway to test INQP mobile setup.May: INQP•QSOs: 276•Points: 548•Mults: 63•Score: 34,524•States and Provinces multipliers: 48•Indiana County multipliers: 15Op Time: 6 hoursIn recent years I have operated mobile or portable with Andy K9ELF. He would do the phone and I would do the CW. This year I was only available in the morning and afternoon and he was only available in the evening. So, no partnership was possible. My XYL agreed to be my driver and an 11 county, half-day mobile operation was planned with the expectation that activity would be limited to 20 and 40 CW. Unlike previous years there were no county line operations planned, so every contact would result in just a single QSO instead of 2 QSOs. The goal was to call CQ on 40M and then move to 20M and CQ there to give both close in and distant stations the chance to snag the multipliers I would be providing.We hit our first county, White, right as the contest started and the rate was brisk. It was, in fact, the best of the contest, logging 62 QSOs the first hour. The second hour was almost as good with 57 QSOs in the log. I noticed, however, that I was primarily logging out-of-state stations, even on 40M, and that ended up being the story of the day. Bands were long and in-state QSOs were hard to come by. When I could hear the in-state stuff, it was invariably weak. Even N9FN, who normally is very loud in the INQP, was difficult to hear. One surprising exception was KJ9C/m who was in Knox county when I worked him just 30 minutes after the start of the contest. He was incredibly loud and I thought, all right, it’s gonna be a great day. But I was only able to work him one other time and even then it was at ESP levels.The XYL had committed to a 5-hour operation and we were back home as planned at 2000z. She jumped out of the car and I headed to Carroll County to park and operate as I had agreed to that activation. I made a quick 14 QSOs there and headed for home, stopping for a bit in White County to log a few more Qs there for the benefit of anyone who had missed me the first time through. I was about ready to pack it in when I came across K9IZ/m who was also surprisingly loud and on a county line to boot. I got him in the log and decided that must be a sign since I was out of time. I had made my last QSO of the day.I found the 7QPs stations were their usual cordial selves, with lots of them in my log. I only had an hour overlap with the NEQP and, by contrast, I found it much more difficult to get them in the log. Perhaps someday someone will come up with an explanation for this difference.Highlight of the day: the Knox County QSO with KJ9C. Knox is the last county I need confirmed to qualify for the Worked All Indiana award.Lowlight of the day: when I got to Vermillion I mistakenly programmed N1MM to report that I was in Vigo County. I will mark these QSOs as Vermillion when I upload to LOTW and will confirm that I was in Vermillion should anyone send me a card. But if you needed Vigo and you worked me, then I apologize for the error; hopefully you were able work a REAL Vigo station sometime that day.Observation: some of the wind turbines in northern Indiana put out a lot of RF noise. In a couple of cases I had to stop operating until we were well past the offender.May: CWOps CWT 1300Z May 16•QSOs: 52•Mults: 49•Score: 2,548Op Time: 30 minutesSession 28 for 2018. May: CWOps CWT 1300Z May 23•QSOs: 54•Mults: 54•Score: 2,916Op Time: 30 minutesSession 29 for 2018. May: CWOps CWT 1900Z May 23•QSOs: 89•Mults: 75•Score: 6,675Op Time: 60 minutesSession 30 for 2018. Called CQ on 20M for several minutes at start of contest with no replies so this cut into my overall rate. Went to S&P and rates were good. Then called CQ (still on 20M) and got some takers. Not sure why 20M was a dud at the start.