BIZTRAC BETA
COMPANY REGISTER PROFILE
932837897 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

STENEBREW AS

Org. no. 932837897 Limited company (AS) Rauma Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 16,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

STENEBREW AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 932837897. 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: “Eie aksjer og investere i virksomheter av enhver art, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 16,000
Est. value
NOK 19,000

Financial health · 2025

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

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

Who owns STENEBREW AS?

STENEBREW AS
NOK 0 rev. · NOK −5,000 profit

STENEBREW AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STENEBREW AS own?

STENEBREW AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STENEBREW AS

Who owns STENEBREW AS?

GAUTE STENERUD is the largest registered owner, with 100.0%.

What is the revenue of STENEBREW AS?

STENEBREW AS had revenue of NOK 0 in 2025.

Where is STENEBREW AS based?

STENEBREW AS has its business address in Innfjorden.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.