BIZTRAC BETA
COMPANY REGISTER PROFILE
931626418 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

ANB AS

Org. no. 931626418 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK −37,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

ANB AS is registered as a limited company in Bærum, Akershus with organisation number 931626418. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Selskapets formål er å investere i aksjer, andre finansinstrumenter og annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Former names: AFAS 060623-07 AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK −37,000

Financial health · 2025

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

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

Who owns ANB AS?

ANITA NATLAND BERG
ANB AS
NOK 0 rev. · NOK −6,000 profit

ANB AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ANB AS

Who owns ANB AS?

ANITA NATLAND BERG is the largest registered owner, with 50.0%.

What is the revenue of ANB AS?

ANB AS had revenue of NOK 0 in 2025.

Who is the general manager of ANB AS?

Anita Natland Berg is registered as general manager of ANB AS.

Where is ANB AS based?

ANB AS has its business address in Blommenholm.

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.