BIZTRAC BETA
COMPANY REGISTER PROFILE
969952890 ORG. NO. 2003 ACCOUNTS 10 SECTIONS
Active UPDATED 02.09.2026
Fire service activities

BRANNVESENET SØR IKS

Org. no. 969952890 Inter-municipal company (IKS) Lindesnes Incorporated 2002 Active
Ownership graph ↗
Incorporated 2002
Employees 189

BRANNVESENET SØR IKS is registered as a inter-municipal company in Lindesnes, Agder with organisation number 969952890. The business is classified under fire service activities (NACE 84.250). The company was incorporated in 2002 and has 189 registered employees. The company's stated purpose is: “Ivareta eierkommunenes behov, plikter og oppgaver vedrørende brann- og ulykkesberedskap, brannforebyggende- og kontrollerende art samt andre tiltak som naturlig hører inn under dette formål innenfor det til en hver tid gjeldende regelverk. Primært er BvS opprettet for å dekke eierkommunenes behov, men tilsvarende tjenester kan også ytes mot vederlag til andre kommuner eller virksomheter.”.

Former names: FELLESBRANNVESENET FOR MANDALREGIONEN

Who owns BRANNVESENET SØR IKS?

No shareholders are registered for BRANNVESENET SØR IKS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BRANNVESENET SØR IKS

Who is the general manager of BRANNVESENET SØR IKS?

Terje Spilling is registered as general manager of BRANNVESENET SØR IKS.

Where is BRANNVESENET SØR IKS based?

BRANNVESENET SØR IKS has its business address in Mandal.

Property

Business address Sorenskriver Fridrichsens gate 7, 4514 Mandal
Cadastral unit 4205-160/1395/0/0

2 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.