BIZTRAC BETA
Uoppgitt

BADSTUGGU AS

Org. no. 922675872 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −559,000
Equity NOK 381.5m
Incorporated 2019
Share capital NOK 204,000

Signals

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

BADSTUGGU AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922675872. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 204,000, divided into 6000 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investeringer i aksjer og verdipapirer i andre selskaper og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −559,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −559,000
Equity
NOK 381.5m
Est. value
NOK 394.9m

Financial health · 2025

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

Who owns BADSTUGGU AS?

THERESE LANGSETH
BADSTUGGU AS
NOK 0 rev. · NOK −559,000 profit

BADSTUGGU AS has 5 registered shareholders:

All shareholders and roles →

Which companies does BADSTUGGU AS own?

BADSTUGGU AS holds stakes in 23 companies:

See the full ownership structure →

Frequently asked questions about BADSTUGGU AS

Who owns BADSTUGGU AS?

THERESE LANGSETH is the largest registered owner, with 33.3%.

What is the revenue of BADSTUGGU AS?

BADSTUGGU AS had revenue of NOK 0 in 2025.

Who is the general manager of BADSTUGGU AS?

Erik Langseth is registered as general manager of BADSTUGGU AS.

Where is BADSTUGGU AS based?

BADSTUGGU AS has its business address in Trondheim.

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.