biztrac. BETA
COMPANY REGISTER PROFILE
934747356 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

RINGBRING AS

Org. no. 934747356 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 9.6m
Operating profit NOK 88,000
Equity NOK 97,000
Incorporated 2024
Share capital NOK 30,000

RINGBRING AS is registered as a limited company in Oslo, Oslo with organisation number 934747356. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen godstransport på vei - 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 9.6m in revenue and NOK 88,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.6m
Operating profit
NOK 88,000
▲ +1625 %
Equity
NOK 97,000
▲ +300 %
Est. value
NOK 347,000

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
10.4%
Good
Return on total assets
Solidity
5.6%
Weak
Equity as a share of total capital

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

Who owns RINGBRING AS?

RINGBRING AS
NOK 9.6m rev. · NOK 88,000 profit

RINGBRING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RINGBRING AS

Who owns RINGBRING AS?

Malik Shair Zaman is the largest registered owner, with 50.0%.

What is the revenue of RINGBRING AS?

RINGBRING AS had revenue of NOK 9.6m in 2025.

Who is the general manager of RINGBRING AS?

Ali Butt is registered as general manager of RINGBRING AS.

Where is RINGBRING AS based?

RINGBRING 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 03.10.2026.

Report a problem

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