BIZTRAC BETA
Retail sale of hardware, building materials, paints and glass

NILSENS BRANNSERVICE AS

Org. no. 930507202 Limited company (AS) Arendal Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 183,000
Equity NOK 389,000
Incorporated 2022
Share capital NOK 50,000

NILSENS BRANNSERVICE AS is registered as a limited company in Arendal, Agder with organisation number 930507202. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 2022. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Salg og kontroll av brannslukningsapparater, brannslanger. Fylling av pulverapparater, CO2-apparater og tilsvarende.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 183,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 183,000
Equity
NOK 389,000
Est. value
NOK 807,000

Financial health · 2024

Liquidity
1.67
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
53.7%
Very good
Equity as a share of total capital

Who owns NILSENS BRANNSERVICE AS?

TOMMY NILSEN
NILSENS BRANNSERVICE AS
NOK 1.2m rev. · NOK 183,000 profit

NILSENS BRANNSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NILSENS BRANNSERVICE AS

Who owns NILSENS BRANNSERVICE AS?

TOMMY NILSEN is the largest registered owner, with 100.0%.

What is the revenue of NILSENS BRANNSERVICE AS?

NILSENS BRANNSERVICE AS had revenue of NOK 1.2m in 2024.

Who is the general manager of NILSENS BRANNSERVICE AS?

Tommy Nilsen is registered as general manager of NILSENS BRANNSERVICE AS.

Where is NILSENS BRANNSERVICE AS based?

NILSENS BRANNSERVICE AS has its business address in Bjorbekk.

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

Report a problem

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