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

STEINGRIM GEVINST AS

Org. no. 934882342 Limited company (AS) Stavanger Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −533
Equity NOK 29,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

STEINGRIM GEVINST AS is registered as a limited company in Stavanger, Rogaland with organisation number 934882342. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med investering i aksjer og verdipapirer, inkludert, men ikke begrenset til, kjøp, salg og forvaltning av aksjer, obligasjoner, derivater og andre finansielle instrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −533 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −533
Equity
NOK 29,000
Est. value
NOK 35,000

Financial health · 2025

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

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

Who owns STEINGRIM GEVINST AS?

STEINGRIM GEVINST AS
NOK 0 rev. · NOK −533 profit

STEINGRIM GEVINST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STEINGRIM GEVINST AS

Who owns STEINGRIM GEVINST AS?

EMIL VIKØREN VARMBO is the largest registered owner, with 100.0%.

What is the revenue of STEINGRIM GEVINST AS?

STEINGRIM GEVINST AS had revenue of NOK 0 in 2025.

Where is STEINGRIM GEVINST AS based?

STEINGRIM GEVINST AS has its business address in Stavanger.

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.