Solo WH Nomad Journey

[Ridagor_Dunedain]

Ahoy there, Capsuleer!

This project began with a simple but ambitious question:
Can a solo pilot build a sustainable and meaningful life deep within EVE’s unpredictable wormhole space?

As a returning pilot, I’ve chosen to undertake this experiment on an Alpha clone, testing the limits of what’s achievable in wormhole space without Omega advantages.

Over time, this experiment evolved into a full-scale expedition in survival, adaptation, and self-sufficiency. My goal is to prove that life in wormhole space isn’t just possible for a solo pilot — it can be deeply rewarding.

Every day in WH space starts the same way: with uncertainty. You scan the system, chart connections, assess risks, and decide whether today brings profit, peril, or both. This blog follows that rhythm — the daily reality of life as a one-man expedition.

The first phase of this journey takes place in a Class 1 wormhole, focusing on establishing a foothold and achieving basic self-sufficiency. Over time, the scope will expand into C2 and C3 systems, exploring higher risks, greater rewards, and more complex logistics.

All posts here are drawn from real operational logs and private records. They’re published retrospectively — which means the story you read lags slightly behind the actual events. This delay lets me reconstruct each stage of the adventure with full context, accuracy, and reflection.

Eventually, the blog will catch up with real time, and the journey will continue in parallel with my ongoing exploration.

I hope you enjoy following this chronicle as much as I enjoy living — and writing — it.

Fly dangerous,
The Cosmic Nomad

Please subscribe to my blog here: https://eveonline.wkfteam.ru/

The Cruiser Concept: The Journey Begins

Pilot’s logbook extract – Day 1.

So, I’ve finally settled on a plan for solo colonization in a C1 wormhole.
I chose a cruiser — my old reliable Caracal, the ship that has carried me through countless sister missions in low-sec. I prepared two fittings for it: the first optimized for decent scanning, and the second for combat, with acceptable DPS.

The plan was to perform refits via a mobile depot, which I intended to hide inside a secured container at a safe spot in space (if only that were possible!) — containers can’t be scanned by probes. This same container would store loot, allowing me to occasionally haul it back to a trade hub.

Now… it’s time to set out and find my C1!

The first real experience in Cruiser

Pilot’s logbook extract, Day 2.

I began the search in my trusty scanning Heron, looking for a good C1 wormhole to settle in — something quiet enough to live in, but connected enough to make logistics possible. After a bit of wandering, I found one promising system and decided to stay there in the Heron for a couple of days, just to see if it was actually livable and (relatively!) safe.

The system I chose — my new C1 home — has a static to low-sec. Which means that unless I open a new hole myself, absolutely no one drops by. Not a soul. Yesterday I pulled in around 30 million ISK in loot in just half an hour. Later I scanned down an exit and opened a connection to a neighboring system. It turned out to be another C1, this one with a high-sec static… and of course, the moment I poked my nose in, a Stratios showed up. The Sisters’ cruiser. And naturally, he followed me straight back into my system.

I had to bounce to a safe spot and log off for a bit. Survival first!

Anyway — yesterday I finally moved my cruiser into the C1, just as planned. I took it out to run my very first combat anomaly inside a wormhole. And honestly? The ship performed beautifully. :: My shield booster held just barely long enough for me to turn around and warp out without losing the ship. A perfect, elegant escape!

Introduction of Battlecruiser

== Extract from R&D Division Report: Evaluation of Cruiser-Class Efficiency in C1 Systems ==

The expedition has completed the first phase of an experiment focused on permanent solo habitation in a Class 1 wormhole system using a cruiser-class vessel. The initial concept relied on a mobile depot and a cargo container to enable rapid switching between two fittings: a scanning configuration and a combat configuration.

Summary conclusions: the concept has been deemed non-viable; however, a simpler and more practical approach has been identified.

Results of Phase One Testing

In addition to minor logistical issues—such as the loss of a cargo container that broke free from its anchor and drifted irretrievably into deep space—the expedition encountered three major strategic limitations:

1. Limited combat effectiveness of the cruiser.
   Testing confirmed that a T1 cruiser lacks sufficient firepower to complete all combat anomalies in C1 systems. The most challenging sites, whose difficulty approaches that of lower-tier C2 anomalies, proved particularly problematic.
   While the ship’s tank was adequate to withstand the first two waves—allowing the combat pilot to disengage safely without risking hull loss—the third and final wave required significantly greater damage output and survivability. Calculations indicate that a T1 battlecruiser should be able to clear these anomalies without critical difficulty.

2. Insufficient hacking capability.
   Even when using specialized T1 scanning frigates, virus strength and coherence are not always sufficient to reliably hack data and relic sites within the C1–C3 range. In a cruiser-based scanning fit, hacking attempts were assessed as impractical and economically unjustified.

3. Inefficient refitting logistics.
   Refitting via a mobile depot was found to be inefficient. The time required to swap fittings exceeds that of switching to an alternate pilot. Moreover, the presence of a dedicated scanning alt within the system is considered mandatory for operational security: in the event of wormhole collapse, it is the only reliable means of locating a route back to the home system.

It was also determined that the total number of combat and exploration anomalies in C1 systems is insufficient even for a single active pilot. Over the long term, this renders the deployment of a permanent base (POS) in such systems impractical. Relocation to a Class 2 wormhole is therefore recommended.

== End of R&D Division Report Extract ==

The Admiral dimmed the report display and paused to reflect. A new wormhole operational model was beginning to take shape: a combination of a powerful battlecruiser for combat operations and a separate alt pilot dedicated to scanning and hacking, with modules and loot stored in a single shared cargo container.

The mobile depot might still serve a purpose—as a tool for refitting the combat ship into a salvage configuration—but this would require a separate assessment of potential profitability.

The next logical step would be to integrate ore and gas harvesting into the operation and, with it, to address the question of transportation. Once mining and gas extraction are introduced, cargo volumes increase sharply. Only after resolving these issues would it make sense to seriously consider relocation to a C2 system and the deployment of a permanent base.

<To be continued…>

See more and subscribe at https://eveonline.wkfteam.ru/

[Lesican]

@Ridagor_Dunedain

—

beep boop

[DeMichael_Crimson]

Nicely written project report…

[Ridagor_Dunedain]

thank you! Stay tuned, I am working on the next report, will publish this week

[Ridagor_Dunedain]

The EVE Pulse news division, operating from a long-forgotten J-system, reports: the experiment of living off a single cargo container is still ongoing – and so far, it appears to yield reasonable results.

A battlecruiser – a passively fitted Drake – assigned to patrol local space has once again proven its worth. During a recent raid on an abandoned storage site of the ancient Sleepers civilization , the ship delivered an exceptional performance, clearing all three waves of hostile forces in under ten minutes.

Even more intriguing, however, is the report from a scout pilot . According to his report, at some point the system contained an unusually high number of data site anomalies , belonging to a wide range of pirate factions – from the blood-soaked Blood Raiders to the serpent-worshipping Serpentis.

While data sites are typically considered less lucrative than relic sites, fortune favored the explorer this time. One of the containers yielded a blueprint for a unique module , combining the functions of both a relic analyzer and a data analyzer into a single unit. Market rumors suggest that a single such module could be worth around 300 million ISK , and the discovered blueprint allows for the production of three copies.

If these prices hold true, even one manufactured module would fully cover the total value of the entire fleet stationed in the system. All three together would more than double the overall capital of the operation .

Stay with EVE Pulse to keep up with the latest reports from the depths of EVE Online.

Subscribe and read additional technical footnotes here.

[Ridagor_Dunedain]

Excerpt from the Admiral’s Personal Log

The first and most important advantage of life in wormhole space is the profound sense of ownership.
Not in a legal or formal sense, but in a practical and psychological one: a single pilot in the vastness of the cluster calls this system home, even though other pilots may pass through from time to time.

The second key factor is content concentration.
A single system can provide a complete spectrum of activities of strategic value:

• Scanning and combat anomalies — the primary reason for choosing wormhole space. They are complex enough to demand focus and discipline, and profitable enough to justify the risk.
• Gas clouds and asteroid belts — activities that held little practical value in high-sec, but show real potential when approached from within a wormhole ecosystem.
• The prospect of planetary and industrial production — the next step toward true autonomy, requiring a transition to a corporate structure and the deployment of permanent infrastructure.

From there, the question of PvP inevitably arises.
Diversionary operations using stealth bombers are nearly impossible to conduct solo in k-space, whereas in wormhole space they become a natural extension of daily life: rapid strikes, ambushes, and disappearance into unstable connections.

---

Excerpt from the Admiral’s Strategic Journal

Minimum Role Set for Autonomous WH Living

Phase One: PvE and Reconnaissance

Combat Vessel (Damage Dealer)

• C1 — a battlecruiser is sufficient.
• C2 — a BC is viable, but coordinated setups are preferable:
  a battleship with logistics support, dual battlecruisers, or a battleship paired with an anti-frigate platform. However this would require some friendly pilots.
• C3 — multiple battlecruisers or battleships with proper support.

Scanning and Hacking
A mandatory role. A cloaked vessel is a strategic advantage and the standard for long-term presence, though at this stage the clone lacks the necessary capabilities.

Phase Two: Expanding Income and Autonomy

• Salvaging can be handled by refitting existing ships.
• Gas and ore harvesting — from Ventures to barges, depending on acceptable risk and investment.
• Logistics — ideally via Deep Space Transports or Blockade Runners, though for now T1 solutions are sufficient.

Phase Three: Expansion and Warfare

• Light PvP in hostile territory — diversion, piracy, and pressure, primarily through stealth bombers.
• Defensive forces — inexpensive frigates, destroyers, and cruisers for rapid response to incoming forces.
• Strike fleets — no longer a solo concern, but a matter of collective strategy; premature to consider at this time.

---

The admiral closed both journals and paused.

• For a C1-class system, the current minimal role set satisfies all essential needs and scales naturally into C2. All of this can be achieved without establishing a permanent base, relying instead on temporary storage — cargo containers or mobile depots. The industrial model assumes the use of a secondary pilot as a logistics asset: ships are pre-positioned in major trade hubs, enabling cyclical import and export of materials. A mobile depot allows rapid transitions between gas harvesting, mining, and salvaging operations. The shift toward active PvP and advanced industry requires an upgrade to clone status. That step, in turn, unlocks planetary production — the foundation of a truly autonomous economy.

The automated viewport dimming system, simulating a planetary day-night cycle, began to lift its filters. Light from the nearest star spilled into the command deck — the star that gave warmth and energy to the system the admiral called Home.

It was Christmas morning
on one planet far, far away.

[Ezra_Endashi]

Wow, such a interesting journal! Loved reading it. Now I’m watching for future updates. I was thinking of living solo in a WH for so long but never encouraged myself to really do it. Your journal might help to do that final decision and kick off the endeavor.

[Ridagor_Dunedain]

The first industry reports

Several reports on resource extraction in the C1 system lay on the admiral’s desk, awaiting his attention.

Resource Extraction and Production Department Report

Status: preliminary assessment. As part of ensuring the expedition’s autonomy, an analysis of available resource sources within the system was conducted. The objective of this assessment was to determine the viability of industrial activity in a Class 1 wormhole under a solo crew setup.

Initial Conditions

Assets: Venture-class frigate with bonuses to ore and stellar gas extraction
Objective: utilize local resources as an additional source of income
Hypothesis: a mobile depot would allow a single ship to adapt to multiple tasks without leaving the system
It was assumed that the Venture could be used for ore and gas extraction and, when necessary, for salvaging, by reconfiguring the ship directly in-system.

Platform Limitations

Analysis showed that the primary limitation was the ship’s standard cargo hold. It can accommodate a mobile depot, but leaves no space for storing spare modules. Specialized ore and gas holds partially offset this limitation, but they are not applicable to salvaging operations.
As a result, a universal configuration proved impractical. The ship must remain focused on a single task at any given time. Based on this, it was recommended to conduct separate trials for each type of resource extraction and evaluate their effectiveness individually.

Excerpt from the Pilot’s Personal Log

The asteroid field was striking in its scale. Dozens upon dozens of asteroids scattered through space, like the frozen remains of an ancient catastrophe. Each one could be mined for hours, and for a moment it felt as though there were more resources here than I could extract during my entire stay in the system.

But the longer the mining lasers ran, the clearer another realization became. The cargo hold filled slowly, and the value of the ore did not justify the time invested.

Gas anomalies left a different impression. The cloud of stellar gas looked almost alive. In twenty minutes of operation, roughly half the hold was filled, with an estimated market value of around ten million ISK. The process was calm, almost meditative, but required constant attention and extended time on site.

End of Pilot’s Log Excerpt

The admiral closed both reports and paused. Ore extraction showed low efficiency despite the abundance of resources. Gas proved more valuable, but its slow pace and elevated risk made it unsuitable as a primary activity in wormhole space. Both options demanded time, a resource that is often in short supply in a C1 system.

At this stage, a decision was made to abandon industrial activity in the C1 system.

As a supplementary source of income requiring minimal time investment, salvaging the remains of combat operations was retained. The expedition was instructed to make a run to a high-sec trade hub and acquire a dedicated ship fully focused on salvaging tasks. The Resource Extraction Department was ordered to consider the experiment concluded.

[Ridagor_Dunedain]

The Only Citadel in the System

C1 systems are rarely popular among capsuleers. Throughout the entire period of exploration here, only a single permanent structure was recorded: a citadel drifting far from the main navigation routes.
Until now, it existed merely as a database entry. No history. No status. No answers.

Reconnaissance was assigned to an industrial pilot. His ship was considered the most expendable, although the admiral, of course, did not mention this aloud. Officially, the task was simple: approach the structure, identify its type, and assess the situation. Unofficially, everyone understood that an active citadel shows no signs of life until someone actually mans its weapons. In wormhole space, silence is never the same as safety.
The pilot dropped out of warp at a safe distance. The citadel hung motionless in the void, as if forgotten. No ships nearby. No signs of recent activity. No visible indicators of active defensive systems. He began to close the distance slowly with all systems on high alert. There was no response.
The mere existence of the station altered the balance of power in the system. A silent citadel could become a future threat, a potential source of loot, or simply a reminder that someone once lived here and left without explanation.
The pilot recorded the coordinates and warped out, without trying to find answers that did not yet exist.
And yet, the feeling persisted that the citadel might be abandoned. If that were true, then, at least in theory, it could be destroyed by fitting a ship with damage output exceeding its passive regeneration.

When the report reached the admiral’s desk, one thing became clear.
The question was no longer whether the structure was dangerous.
It could become dangerous at any moment.
The real question was different.
Was it worth testing that assumption right now?

[Ridagor_Dunedain]

Should I stay or should I go?

News from our enclave in a lost star system.

The Research and Development Division has completed its analysis of a potential operation to eliminate the resident citadel (see the previous report). The final report turned out to be… discouraging. With the current capabilities of the combat capsuleer, the outgoing damage of a single pilot is insufficient to overcome shield regeneration. This is under the most optimistic assumptions: the citadel is inactive, unfueled, and fitted with minimal defensive modules.

The conclusion is clear. A successful assault would require unlocking Omega capabilities and training a number of additional skills.

However, this issue extends far beyond a single combat operation. Unlocking Omega status requires approval from the financial committee and simultaneously opens two fundamentally new directions for the expedition. These are planetary industry and the ability to refit the fleet with ships utilizing stealth technologies.

In turn, this inevitably raises a broader and far more complex question: what are our mid-term strategic plans? Should we remain in the current system, or begin searching for a new one of a higher class?

According to preliminary calculations, the expedition in its current composition can operate effectively in systems of classes 1 through 3. Below is a brief summary of the recommendations provided by the R&D experts. The full report has been submitted to the committee for detailed review and decision-making.

Excerpt from R&D Report #37.569 dated 26 Dec 3076 / YC127

C1

Pros:
We are already here. Low population density. An ideal environment to calmly master POS deployment and operation, remove the local citadel, and initiate planetary industry.

Cons:
Combat anomalies gradually lose their appeal for the primary pilot and do not always provide stable income. Relocation to a higher-class system is almost inevitable in the long run, meaning that investments in infrastructure (POS and PI) may not have time to pay off.

C2

Pros:
Systems with a high number of anomalies and wormholes. A rich and diverse selection of anomalies, a wide range of statics leading both to known space and to other wormholes. The option to field a battleship. Anomalies are manageable even with the current battlecruiser, albeit with increased risk.

Cons:
Popular static combinations are often occupied or lead to regular evictions. High system traffic results in a constant presence of transient pilots, complicating infrastructure deployment. At the same time, anomaly income remains on par with C1. In essence, C2 represents a transitional level between C1 and C3, making deep infrastructure investment potentially unjustified.

C3

Pros:
Significantly higher income from combat anomalies. A smaller number of statics allows for a more controlled environment, and the systems themselves are less transient. C3 systems are traditionally considered the peak for micro-expeditions into wormhole space. After that there is only possible transition is to have a null-sec static.

Cons:
Opponents in anomalies are considerably stronger, making a battleship a necessity. C3 systems are extremely popular among small and mid-sized corporations, resulting in a high risk of eviction. C3 represents both a peak and a potential endpoint of development, so it may be wise not to rush.

End of excerpt

The financial committee will provide recommendations to the CEO in the near future to ensure that the decision is balanced and strategically sound. This excerpt has also been distributed to shareholders for the purpose of gathering their opinions.

On the expedition’s official corporate portal, all shareholders are invited to express their position via an online poll.

[Ridagor_Dunedain]

Searching for a New Home

The vote has concluded, and the decision was made to look for a new C2 system. Now it was time to turn that decision into an actual route.

Excerpt from the scout pilot’s private journal

When we were studying at the flight academy, one of the subjects was “History and Mythology of Ancient Civilizations.” Among other things, they told us about a book that likely had a tremendous influence on the culture of our ancestors, and about a phrase from it: “seek and you will find.” Yesterday, I finally understood what it truly meant.

I have never seen so many wormholes at once in a C1 system.

Usually, everything is far more mundane. At best, there is a single wormhole leading deeper into unknown space. More often than not, there is nothing but a static connection to high-sec. But this time, it felt as if the Universe itself, or perhaps the gods from ancient myths, had decided to lend us a hand. Seven wormholes at once.

Two led to high-sec.
One went deeper, into the “Dangerous Unknown” region, meaning C4 or C5 system.
The remaining four looked promising.

The scouting operation began.

The first system turned out to be a C2. Acceptable statics, no permanent residents, but the star had a Wolf Rayet effect. Our expedition’s combat pilot would hardly appreciate those conditions, so the coordinates were recorded and we moved on.

The second system was also a C2. Uninhabited. A red giant star, perfectly workable for daily operations, but potentially problematic for infrastructure. We saved this option as well.

The third system was a C3. An immediate no.

The fourth wormhole looked worse than the rest. It had already begun collapsing and could close at any moment. A jump through it could easily become a one-way trip.

I checked my supplies once more, rechecked the exit coordinates in high-sec, lingered for a second longer than usual, and then pointed the ship straight into the center of the vibrating mass of distorted matter.

On the other side awaited an unremarkable C2 system. No special effects. Statics to high-sec and to a C1.

According to Imperial ship destruction records, a serious fight had taken place here not long ago. Seven ships on each side, which is no small thing for forgotten space. Aside from that, the system appeared empty. No citadels. Only three POS towers. The planetary customs offices belonged to a corporation whose pilots had not appeared in loss reports for a long time.

Silence after the battle.

It seems we have found what we were looking for.

End of the captain’s journal excerpt.

[Ridagor_Dunedain]

The Home I Left Behind

There is a strange feeling that comes after leaving a place you once called home.

By the time the decision had fully materialized, the combat pilot and the scout had already departed from our old C1 system. The system that, for a time, had been ours. The one whose static we knew by heart.

Only the salvager pilot remained behind. He stayed to watch the entrance, in case we changed our minds and decided to return. In case we chose to finish what we had started and finally destroy that citadel. In case “leaving” turned out to mean “not yet.”

He retrieved the remaining loot from the container, perhaps opening it for the last time, and then warped off into deep space. In thirty days, the container will self-destruct.

An explosion noone to witness. A final signal noone to catch. Just a quiet removal from the fabric of space, as if we had never been there.

The pilot will remain, suspended in a kind of dormant watch. Not truly present, yet not entirely gone. A silent placeholder in a system that is no longer ours.

Until he is needed again. On a new base. Wherever that base may be.

[JamieFPG]

Enjoying your adventure - inspiring me to do my own.

[Ridagor_Dunedain]

Securing the New System

The Admiral reviewed the latest reports from the expedition to the lost stars.

This was the system, scouted in the last report. A C2 with no environmental effects, statics to high-sec and to a C1. According to the Imperial killboard, a seven-versus-seven engagement had taken place here not long ago. In wormhole space, that is not an accident. It is a trace.

The combat pilot and the scout confirmed the system’s parameters. Class and statics are acceptable. No additional effects. A missile- and shield-oriented fleet will operate without penalties.
On paper, the system fits.

The logistics report was concise. A medium secure container has been delivered and anchored at a safe location. It is intended for blue loot and hacking sites proceeds, but its real advantage lies elsewhere: it fits into the hold of a scanning frigate. It does not bind the expedition to this system.
Unlike the giant container left behind in the former C1. It was simply unpractical to get it out of there.
If the system proves inhabited, withdrawal must be swift.

The combat report followed. First anomaly cleared. No losses. No external interference detected.
For now.

The Admiral closed the report.
How long does one have to remain in a system to consider it empty? A day? A week? A month?
In wormhole space, silence is rarely vacant.

[Ridagor_Dunedain]

C2 Security and Habitability Review

Admiral’s desk was covered with a stack of reports from the C2 expedition.

Reports on cleared anomalies: difficult, but manageable. In one engagement the pilot had to warp out to regenerate shields, but the ship is intact. An acceptable operational risk.

Reports on data and relic sites are more interesting. Over 100 million ISK from a single anomaly. The total value of the loot stored in the container is approaching 300 million. It may be time to organize a transport to a trade hub while luck is still on our side.

A separate report details a deep reconnaissance run. The pilot moved more than five wormhole jumps away from the home system. A bold move. Good that the route did not collapse behind him. But on the other hand, this is exactly the kind of exploration the expedition was created for.

There is also a note that some anomalies had been cleared before our arrival.

Next come extracts from imperial kill board for ships lost in our system recently.

• Venture. Expected.
• Deep Space Transport. More interesting. Either someone’s logistics chain passed through the system and ran into trouble, or the system is not as empty as it first appeared.

Reports of potential threats follow. The admiral spent more time reading this section.

• Cheetah. A scanner? Then why no probes deployed? A hunter? Bait? Recon under disguise?
• Tengu. The workhorse of unknown space. It can be a scout, a hunter, or a strike ship. This report came from our reconnaissance pilot; the ship was spotted outside our home system. For now, that is somewhat reassuring.
• A Triglavian fleet?..

The admiral read the report twice.

“Switched directional scan to a wider filter.”
“Multiple groups of contacts scattered across the system.”
“Exact locations unknown. Combat probes required.”

The admiral requested an analytical briefing.

After the Triglavian Invasion they secured several systems in the Pochven region, but their forces are still occasionally reported outside it. In wormhole space, small Triglavian patrols and fleets do appear from time to time. These are usually roaming combat groups, not connected to capsuleer infrastructure. They may guard certain anomalies or appear as separate combat signatures. Their presence in wormhole space is rare, but not a myth.

Which means the report is likely credible.

The real question is different: should we try to find them deliberately? Encounters like that may cost more than a ship. They may cost us the initiative in the system.

The admiral leaned back in his chair.

The C2 system matches expectations: many anomalies, strong connectivity, constant traffic. There is plenty of content to explore. And plenty of neighbors as well.

What should we do next?

Wait?

Activity in the system remains high. The destroyed transport and the signs of previous clearing suggest that we are not alone here. Perhaps the best option is to exploit the system’s connectivity for scanning and capital accumulation without committing to a permanent presence.

Upgrade to Omega, install a cloak, and move to T2 scanning?

Income from exploration would increase, risks would decrease. It would also allow safer investigation of the Triglavian signatures and open the path to planetary industry. But that would also be a step toward long-term presence.

Deploy a POS?

Even if the system turns out to be inhabited, establishing a base would provide valuable experience and a strategic foothold in a C2 environment.

Or search for another C2 system with a different static configuration, something quieter and more isolated? Less traffic. Lower risk of eviction. But fewer opportunities as well.

The admiral slowly placed the reports back into the folder.

Are we ready to settle here? Are we willing to accept higher risk in exchange for faster growth? Or is caution still the wiser choice? There are questions, but no easy answers.

[Ridagor_Dunedain]

Watching the Dangers of Wormholes

== Pilot’s personal log extract ==

Over the past few days, I have seen more ships in wormhole space than I had in a long time. Three times I was hunted with combat probes, and once I found myself in direct sight of a pirate cruiser while scouting.

But let me put it all in order.

Day One.
Objective: find a high-sec exit within a reasonable distance from Osmon, where the rest of the fleet was based. A pilot needed to be left there to handle the legal formalities of corporation registration.

Our static led to a system four jumps away from Amarr. Too far from the objective, so I returned and continued scanning. In addition to the high-sec exit, I found two wormholes leading to C1 systems.

The first system turned out to be unexpectedly rich: multiple anomalies, two relic sites, one data site. But as I pushed deeper, combat probes appeared on d-scan. A clear sign the system was inhabited and its residents were not welcoming. I shut down my activity and returned home.

The second C1 provided the exit I needed. Day complete.

Day Two.
The objective became more complex: I needed two exits at once – one near Amarr to pick up a production pilot, and another near Osmon to return a companion.

From the very beginning, the day did not go as planned.

A Typhoon battleship appeared on d-scan. I checked combat anomalies and located its position. Unpleasant, but not critical, so I continued scanning, as unlikely he would be after me.

But then the situation escalated quickly. A Buzzard entered the system, launched probes, and cloaked. A few minutes later – an Anathema. And this time, with combat probes. I immediately stopped all activity, warped to a safe spot, and began observing.

Soon after, a full fleet entered the system: battleship, battlecruiser, cruiser, and frigate. The Typhoon did not last long: a capsule briefly appeared on d-scan and then disappeared.

Then the Anathema launched combat probes again. No doubt this time, I was the target. After several warps between safes, I saved all scanned signatures and slipped into hibernation.

Later that same day, I resumed the search. From the home system, I had exits to a C1 and a C2. I checked the C1 first: several wormholes, but while inspecting one of them, I encountered a pirate cruiser with an active suspect flag sitting on the wormhole. That was enough not to linger any longer.

I moved on to the C2. And there, I found a real surprise. It was a C2 with statics to low-sec and another C2 – exactly the configuration I had originally been looking for. Quiet, yet highly connected: at least two guaranteed wormhole systems at any time, which meant stable chains and likely access to high-sec exits. For a moment, I even considered packing up and relocating. The system was full of wormholes. But one of them eventually led to a high-sec exit just two jumps from Amarr, so I continued with the original plan.

Day Three.
Without major incidents, I opened another exit near Osmon.

== End of pilot’s personal log extract. ==

The Admiral paused for a moment. The first phase of the operation was complete. They were ready for the next step.

[Ridagor_Dunedain]

Starbase to be!

The Admiral was reviewing two reports from the stellar enclave.

Combat report

The combat report arrived first.

Over the weekend, our scout pilot found himself the target of a Tengu — the strategic cruiser that serves as the universal workhorse of wormhole space. He spotted it during routine scanning. Combat probes appeared almost immediately after. He did not panic. Moving between safe spots, narrowing his d-scan radius, he confirmed what he already suspected: the probes were looking for him. He slipped into hibernation.

When he returned, the relic anomalies were untouched. Including one he had already pre-scanned — approximately 80 million ISK sitting in open containers, unmolested. The hunter had not claimed a single site. That detail mattered more than the threat itself: this was not a resident. This was a visitor passing through on his own business.

The enclave’s working hypothesis holds. High traffic does not mean inhabited. The difference is significant.

The decision stands confirmed – we setup POS in this system.

Planning and logistics report

The planning and logistics department submitted its cost estimate for a small starbase. Total figure: approximately 200 million ISK. The Amarrian tower was selected — maximum power output and laser weapon bonuses, which means no ammunition dependency.

The analysis team modelled several siege scenarios. The conclusion was counterintuitive. Raw defensive firepower is not the decisive variable. What matters is the cost calculation for an attacker: how long will the assault take, and does the potential reward justify it? ECM modules and resistance profiles shift that calculation far more effectively than additional guns.

There is a complication. Defence modules and a corporate hangar array cannot both be fitted within the available powergrid. One or the other. Logistics infrastructure, or the ability to hold off a serious incursion.

The choice will have to be made before the first delivery run.

[Ridagor_Dunedain]

POS is up!

Operational reports from enclave: the POS installation took several days.

Stage One. Finding the exit.

The objective was straightforward to state and difficult to execute: locate a high-sec wormhole within practical distance of Jita.

It began with the pilot scanning the home system. The high-sec static led into Minmatar space, but it was already at the end of life and could collapse at any moment. The pilot moved on to a neighboring C1, where no fewer than eight wormholes were detected, so the scan took time. Each connection had to be checked, along with the adjacent systems beyond them. In the end, no suitable exit was found.

Meanwhile, a new signature appeared in the home system: another wormhole to a C1. By the time the pilot reached it, two wormholes on the other side showed clear signs of significant mass disruption: one leading to high-sec, the other deeper into wormhole space, likely C4 or even C5.

There was only one conclusion. A logistics route from a stronger corporation had recently passed through this system. Which meant the high-sec exit should be close to a major trade hub.

It was. Four jumps from Jita.

Stage Two. The logistics problem.

Procurement revealed the first complication. The total volume and value of materials (the tower, fuel, ship hangar, combat modules, strontium, etc.) exceeded the capacity of a single T1 transport. And even if it had fit, a fully loaded transport of that value would have been an obvious target.

The operation was split into two independent transports and several smaller runs.

The first transport carried the tower and a minimal fuel supply. Total cargo value: approximately 200 million ISK. The fit was optimised for speed: align time reduced to five seconds. Not sufficient to escape a well-organised camp, but enough to exploit hesitation. The second transport carried the ship hangar. Large, slow, inexpensive. Mobility was sacrificed to make it fit. The remaining modules, additional fuel and strontium were divided across several light runs.

Stage Three. The run.

When a wormhole opened twelve jumps from Jita, the plan was set in motion.

The route was mapped. The starmap statistics had revealed destroyed ships in two systems along the path and the killboard confirmed: a Noctis in an asteroid belt, a Deep Space Transport at a gate, a freighter further along. The kill records clearly indicated a nine-pilot fleet under single command, hunting for valuable cargo. The drop from the freighter alone had exceeded one billion ISK. My transport and its contents looked modest by comparison. That was reassuring.

On approach to the first flagged system, I checked the killboard again and there was nothing new. That was not reassuring: it meant they had had time to take position.

Jump, and… The gate was empty. But local showed all nine, criminal flags active.

Feeling the pulse in my veins I issued a warp to the next gate command. At the next gate there was a combat cruiser, which jumped through as I landed. If that was a scout, the following system was already waiting for me.

Jump, and… Empty! Warp engaged… 5 seconds align time… First transport clear!

The remaining runs were quiet. Hangar, modules, fuel, strontium — each delivered without incident.

The tower raised its shields, laser batteries came online. For the first time since the expedition began, the enclave had something in the depths of wormhole space it could call home.

[Ridagor_Dunedain]

Warpath: Strategic Infiltration

== Pilot’s personal log extract ==

The plan for the day was simple: refuel the station. Before leaving, I ran a quick scan of the system — two wormholes, both our known statics, and two data sites I hadn’t seen before. The statics were untouched, which meant no one had come through. I was alone. I decided to check the sites before running logistics.

The first was unremarkable. I hacked it and moved on. The second was not.

Warpath: Strategic Infiltration.

The site contained acceleration gates — already unusual for a data site. I jumped through.

On the other side: a vast complex, dozens of structures scattered across the grid, and eight hackable containers rumoured to hold 10–20 million ISK each. The security layout was unlike anything I had encountered before.

I took a moment to map it. Four distinct node types.

• Sentinel Nodes act as motion detectors: approach too close and the alarm triggers immediately.
• Sentry Nodes are gun batteries that open fire on everything in range the moment the alert goes up.
• Confinement Nodes deploy warp-disruption bubbles, cutting off any possibility of escape.
• And Tripwire Nodes are exactly what they sound like — explosives that detonate when the alarm fires.

And one node to rule them all: a Master Security Node. Hack it after the alarm has already been raised, and it can deactivate the entire system.

Each defensive structure could also be hacked individually. The logic seemed clear enough: disable the guns, stay clear of the motion sensors, and the site becomes workable.

Getting to the Sentry Nodes turned out to be harder than expected. There was no clean warp-in, no safe approach vector. I had to navigate manually, threading between structures at low speed while constantly tracking my distance to every Sentinel on the grid. Not a skill a scanning frigate pilot gets much practice with. I am more accustomed to safe spots and instant warps than to delicate manual flying in the middle of a minefield. Still, I made it. Hacked the gun batteries, approached the first container. Success. Second container. Success again.

The third is where it ended.

A failed hack — and the alarm went live. What fired first, I genuinely do not know. The incoming damage was too heavy and too fast to identify the source. Bubbles went up. Shields and armour dropped quickly. I was in my capsule before I fully understood what had happened.

The capsule couldn’t warp either. The bubbles were still active. Then the Tripwire Nodes detonated — and the blast caught my pod. I came to in my home system, deep in high-sec, with no idea how to get back. I had deliberately left the statics unopened to keep visitors out, which meant I had no saved exit coordinates.

I switched to my second pilot and probed the statics out from that side. They came up inconveniently far, routing through low-sec. Before switching back, I jumped the second ship into the site to check its status — the alarm was still running. The moment I came out of the acceleration gate, the complex opened fire. Shields, armour, structure — all going fast. I barely got out, and the ship needed repairs afterward.

Back on my main, I made the run to Jita, picked up a new scanning frigate, cleared the low-sec route without incident, and returned home. By then the site signature had already despawned — the post-alarm timer had long since expired. I tried to find the wreck anyway, jumping through bookmarks, closing to within six thousand kilometres. Forty minutes on MWD. I decided to complete the single refueling run first before attempting that, but between all of that too much time had passed and the wreck was no longer there. The loot I had pulled from the first two containers had drifted away.

What exactly went wrong when the alarm triggered — I still do not know. A gun battery I missed? The blast radius of a Tripwire I misjudged? A fundamental misreading of how the system works? I have asked the analysis department to pull whatever documentation exists on this site. Next time will be different.

== End of pilot’s personal log extract. ==

[DeMichael_Crimson]

You’ve definitely filed some engaging and thought-provoking reports here…

Keep up the good work..

DMC
o7