BIZTRAC BETA
Computer programming activities

BRANDSAFE AS

Org. no. 996941566 Limited company (AS) Sarpsborg Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK 441,000
Equity NOK 1.1m
Incorporated 2011
Employees 6
Share capital NOK 436,000

BRANDSAFE AS is registered as a limited company in Sarpsborg, Østfold with organisation number 996941566. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2011 and has 6 registered employees. Registered share capital is NOK 436,000, divided into 4360 shares. The company's stated purpose is: “Fremstilling/salg av webbasert/applikasjonsbasert system for produksjon av salgsfremmende produkter og lignende, spesielt rettet mot kjeder, nasjonalt og internasjonalt, produkter og konsulenttjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 441,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
Operating profit
NOK 441,000
Equity
NOK 1.1m
Est. value
NOK 3.1m

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.1%
Good
Equity as a share of total capital

Who owns BRANDSAFE AS?

KARDIGAN AS
BRANDSAFE AS
NOK 6.0m rev. · NOK 441,000 profit

BRANDSAFE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRANDSAFE AS

Who owns BRANDSAFE AS?

KARDIGAN AS is the largest registered owner, with 25.0%.

What is the revenue of BRANDSAFE AS?

BRANDSAFE AS had revenue of NOK 6.0m in 2025.

Where is BRANDSAFE AS based?

BRANDSAFE AS has its business address in Grålum.

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.