A display switch is not a counting rule
Ask the app which objects it included, rather than accepting a larger badge. A visibility setting can reveal a node that was already present in the chart data. That does not create another planet. If an app deliberately counts nodes, its result describes a different object list. Keep that extended count separate from the planet-only result.
This guide addresses an interface failure: several nearby symbols can look like several additional bodies. It does not tell you to ignore the node in an astrological interpretation. The question here is whether an extra symbol should increase a specific numerical count.
Audit a five-row export without counting five members
Use this deliberately constructed example: Mars at 12 degrees Gemini, Jupiter at 16 degrees Gemini, mean North Node at 18 degrees Gemini, true North Node at 19 degrees Gemini, and Ascendant at 22 degrees Gemini. These are invented test inputs, not a calculated historical sky or a reader’s verified birth chart.
The export contains five rows. The planet-only list contains two members: Mars and Jupiter. A separately declared list that includes the North Node contains three distinct objects if you choose one node model. Counting both node rows produces a duplicate representation. Counting the Ascendant as another planet changes the object category again.
At a three-planet threshold, this example does not qualify. With two planets plus one node, you can describe an extended three-object concentration, but the more informative label is the member list itself. Do not silently attach the planet-only verdict to the extended result.
Mean and true node: choose a representation
Lunar nodes mark intersections between the lunar orbital plane and the ecliptic plane. They are calculated locations, not additional orbiting bodies. Mean and true node calculations describe that geometry differently. Their difference can matter to a position-sensitive interpretation; it does not make them two separate North Nodes.
Keep the selected model beside the reported longitude. If two apps use different models, compare the model names before treating their different degrees as a calculation fault. If an exported file includes both models, retain both rows for comparison but assign them the same conceptual identity in your counting audit.
Do not average the two values to invent a third node setting. Near a sign boundary, report each model’s placement separately. The planet-only count remains unaffected by the choice because neither model enters its included-body list.
A practical check before sharing your result
First write down the exact output label: planets, placements, objects or chart points. Those labels are not interchangeable. Next copy the named members. Separate physical bodies and the Sun/Moon luminaries from nodes and angles. Finally remove duplicate representations of one object before checking the selected threshold.
For the example above, save two lines: planet-only members = Mars, Jupiter; additional selected point = true North Node. The Ascendant can remain in a separate angles field. Someone reading this note can reproduce your count without guessing what five symbols meant.
Our stellium calculator reports its included bodies. It does not offer a node-inclusive count. Use it to inspect its stated planet and luminary list; use your chart software’s documented node setting for a separate node comparison. Unknown house information remains unknown and must not be supplied from a sign list.
Reject the claim that exclusion means insignificance
An object can be outside a counting rule without being forbidden from interpretation. A node’s astrological importance is a separate claim from its membership in a planet count. Conversely, adding more symbols does not demonstrate a stronger personality, greater destiny or a more powerful chart.
This audit establishes categories and arithmetic. It does not validate an astrological prediction. Keeping the list explicit avoids both errors: erasing a point because it is not a planet, and promoting every visible point into another planet.
Two questions to settle before interpreting
Can the North and South Nodes both be in one sign group? They are opposite ends of the nodal axis, separated by 180 degrees in the standard representation. They therefore do not occupy the same 30-degree sign. Seeing both names in an export is not evidence of two members of one sign concentration.
What if an app will not show its members? Treat the badge as unaudited. Save the raw positions and ask for the included-object rule. You can still inspect your chart, but you cannot establish that its count agrees with another tool from the number alone.
Sources and original contribution
Geometry and the distinction between mean and true nodes: Swiss Ephemeris documentation. The five-row export, deduplication ledger and two-output audit are original constructed teaching examples. They are not a recovered archive, a client record or a measured sky.