BIZTRAC BETA
Uoppgitt

TO BRINGS AS

Org. no. 930940976 Limited company (AS) Arendal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK −524,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−524k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

TO BRINGS AS is registered as a limited company in Arendal, Agder with organisation number 930940976. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i verdipapirer, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK −524,000

Financial health · 2025

Liquidity
0.53
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-129.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns TO BRINGS AS?

BRINGS AS
TO BRINGS AS
NOK 0 rev. · NOK −9,000 profit

TO BRINGS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TO BRINGS AS own?

TO BRINGS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TO BRINGS AS

Who owns TO BRINGS AS?

BRINGS AS is the largest registered owner, with 50.0%.

What is the revenue of TO BRINGS AS?

TO BRINGS AS had revenue of NOK 0 in 2025.

Who is the general manager of TO BRINGS AS?

Thomas Bringsverd is registered as general manager of TO BRINGS AS.

Where is TO BRINGS AS based?

TO BRINGS AS has its business address in Arendal.

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.