biztrac. BETA
COMPANY REGISTER PROFILE
931510363 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

RINGLA AS

Org. no. 931510363 Limited company (AS) Bergen Incorporated 2023 Active
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2023
Share capital NOK 30,000

RINGLA AS is registered as a limited company in Bergen, Vestland with organisation number 931510363. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen investering i aksjer og verdipapirer - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. 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 30,000
▲ +0 %
Est. value
NOK 35,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
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 RINGLA AS?

RINGLA AS
NOK 0 rev. · NOK 0 profit

RINGLA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RINGLA AS own?

RINGLA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RINGLA AS

Who owns RINGLA AS?

Lasse Ringstad is the largest registered owner, with 100.0%.

What is the revenue of RINGLA AS?

RINGLA AS had revenue of NOK 0 in 2025.

Who is the general manager of RINGLA AS?

Lasse Ringstad is registered as general manager of RINGLA AS.

Where is RINGLA AS based?

RINGLA AS has its business address in Olsvik.

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

Report a problem

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