BIZTRAC BETA
Buying and selling of own real estate

BREDSAND HOLDING AS

Org. no. 989261436 Limited company (AS) Moss Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK 1.9m
Incorporated 2005
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−16k kr).

BREDSAND HOLDING AS is registered as a limited company in Moss, Østfold with organisation number 989261436. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2005. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Investere i eiendom og andre selskaper, utleie, administrasjon, konsulentvirksomhet og hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 1.9m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns BREDSAND HOLDING AS?

JAN ERIK SKOVDAHL
BREDSAND HOLDING AS
NOK 0 rev. · NOK −16,000 profit

BREDSAND HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BREDSAND HOLDING AS own?

BREDSAND HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BREDSAND HOLDING AS

Who owns BREDSAND HOLDING AS?

JAN ERIK SKOVDAHL is the largest registered owner, with 100.0%.

What is the revenue of BREDSAND HOLDING AS?

BREDSAND HOLDING AS had revenue of NOK 0 in 2024.

Where is BREDSAND HOLDING AS based?

BREDSAND HOLDING AS has its business address in Dilling.

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.