BIZTRAC BETA
COMPANY REGISTER PROFILE
932122995 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

BINTS HOLDING AS

Org. no. 932122995 Limited company (AS) Drammen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3,000
Operating profit NOK −4,000
Equity NOK 28,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

BINTS HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 932122995. 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: “Investeringer og forvaltning av investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 3,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 3,000
Operating profit
NOK −4,000
Equity
NOK 28,000
Est. value
NOK 17,000

Financial health · 2025

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

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

Who owns BINTS HOLDING AS?

ANDERS BJØRNERUD
BINTS HOLDING AS
NOK 3,000 rev. · NOK −4,000 profit

BINTS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BINTS HOLDING AS

Who owns BINTS HOLDING AS?

ANDERS BJØRNERUD is the largest registered owner, with 100.0%.

What is the revenue of BINTS HOLDING AS?

BINTS HOLDING AS had revenue of NOK 3,000 in 2025.

Who is the general manager of BINTS HOLDING AS?

Anders Bjørnerud is registered as general manager of BINTS HOLDING AS.

Where is BINTS HOLDING AS based?

BINTS HOLDING AS has its business address in Krokstadelva.

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.