BIZTRAC BETA
Funeral and related activities

BN-MSP AS

Org. no. 832344222 Limited company (AS) Sarpsborg Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −28,000
Equity NOK 1.8m
Incorporated 2023
Share capital NOK 1.8m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−28k kr).

BN-MSP AS is registered as a limited company in Sarpsborg, Østfold with organisation number 832344222. The business is classified under funeral and related activities (NACE 96.300). The company was incorporated in 2023. Registered share capital is NOK 1.8m, divided into 100 shares. The company's stated purpose is: “Investere i aksjer, andeler i selskap etter selskapsloven, utenlandske selskaper, obligasjoner, fast eiendom og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 1.8m
Est. value
NOK 971,000

Financial health · 2025

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

Who owns BN-MSP AS?

NORDLING HOLDING AS
BN-MSP AS
NOK 0 rev. · NOK −28,000 profit

BN-MSP AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BN-MSP AS own?

BN-MSP AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BN-MSP AS

Who owns BN-MSP AS?

NORDLING HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of BN-MSP AS?

BN-MSP AS had revenue of NOK 0 in 2025.

Who is the general manager of BN-MSP AS?

Benjamin Sabah Nordling is registered as general manager of BN-MSP AS.

Where is BN-MSP AS based?

BN-MSP AS has its business address in Sarpsborg.

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.