BIZTRAC BETA
COMPANY REGISTER PROFILE
934882288 ORG. NO. 7 SECTIONS
Active UPDATED 02.09.2026
Retail sale of clothing

NORDIC TACTICAL SUPPLIES AS

Org. no. 934882288 Limited company (AS) Ullensaker Incorporated 2025 Active
Ownership graph ↗
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

NORDIC TACTICAL SUPPLIES AS is registered as a limited company in Ullensaker, Akershus with organisation number 934882288. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen klær, sko og utstyr via netthandel og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Who owns NORDIC TACTICAL SUPPLIES AS?

NORDIC TACTICAL SUPPLIES AS

NORDIC TACTICAL SUPPLIES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDIC TACTICAL SUPPLIES AS

Who owns NORDIC TACTICAL SUPPLIES AS?

CM SECURITY GROUP AS is the largest registered owner, with 100.0%.

Who is the general manager of NORDIC TACTICAL SUPPLIES AS?

Christian Skundberg Moran is registered as general manager of NORDIC TACTICAL SUPPLIES AS.

Where is NORDIC TACTICAL SUPPLIES AS based?

NORDIC TACTICAL SUPPLIES AS has its business address in Kløfta.

Property

Business address Trondheimsvegen - Kløfta 86, 2040 Kløfta
Cadastral unit 3209-29/63/0/0

26 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.