biztrac. BETA
COMPANY REGISTER PROFILE
927208830 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

BRINGSRUD HOLDING AS

Org. no. 927208830 Limited company (AS) Fredrikstad Incorporated 2021 Active
Operating profit NOK −69,000
Equity NOK 30.8m
Incorporated 2021
Share capital NOK 100,000

Signals

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

BRINGSRUD HOLDING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 927208830. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bedriftsrådgivning og annen administrativ rådgivning, samt eie aksjer i andre selskaper, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −69,000
▲ +34 %
Equity
NOK 30.8m
▲ +5 %
Est. value
NOK 29.8m

Financial health · 2025

Liquidity
542.29
Very good
Current assets ÷ current liabilities
Profitability
12.5%
Good
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns BRINGSRUD HOLDING AS?

BRINGSRUD HOLDING AS
· NOK −69,000 profit

BRINGSRUD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BRINGSRUD HOLDING AS own?

BRINGSRUD HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about BRINGSRUD HOLDING AS

Who owns BRINGSRUD HOLDING AS?

Øivind Bringsrud is the largest registered owner, with 100.0%.

Who is the general manager of BRINGSRUD HOLDING AS?

Øivind Bringsrud is registered as general manager of BRINGSRUD HOLDING AS.

Where is BRINGSRUD HOLDING AS based?

BRINGSRUD HOLDING AS has its business address in Kråkerøy.

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

Report a problem

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