BIZTRAC BETA
Uoppgitt

BAUER IS BACK AS

Org. no. 925554278 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −4,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4k kr).
  • Nylig endring 2026-04-22 Adresseendring registrert 2026-04-22.

BAUER IS BACK AS is registered as a limited company in Oslo, Oslo with organisation number 925554278. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere i selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −4,000

Financial health · 2025

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

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

Who owns BAUER IS BACK AS?

Vilde Bauer Andreassen
BAUER IS BACK AS
NOK 0 rev. · NOK 0 profit

BAUER IS BACK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BAUER IS BACK AS own?

BAUER IS BACK AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about BAUER IS BACK AS

Who owns BAUER IS BACK AS?

Vilde Bauer Andreassen is the largest registered owner, with 100.0%.

What is the revenue of BAUER IS BACK AS?

BAUER IS BACK AS had revenue of NOK 0 in 2025.

Who is the general manager of BAUER IS BACK AS?

Vilde Bauer Andreassen is registered as general manager of BAUER IS BACK AS.

Where is BAUER IS BACK AS based?

BAUER IS BACK AS has its business address in Oslo.

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.