BIZTRAC BETA
Graphic design and visual communication activities

RELLIES AS

Org. no. 932852756 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 618,000
Operating profit NOK 56,000
Equity NOK 58,000
Incorporated 2023
Share capital NOK 30,000

RELLIES AS is registered as a limited company in Bærum, Akershus with organisation number 932852756. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapet skal selge varer og tjenester innen grafisk design 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 618,000 in revenue and NOK 56,000 in operating profit.

Key figures · 2025

Revenue
NOK 618,000
Operating profit
NOK 56,000
Equity
NOK 58,000
Est. value
NOK 310,000

Financial health · 2025

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

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

Who owns RELLIES AS?

SCOTT OLE SØRENBYE
RELLIES AS
NOK 618,000 rev. · NOK 56,000 profit

RELLIES AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RELLIES AS

Who owns RELLIES AS?

SCOTT OLE SØRENBYE is the largest registered owner, with 50.0%.

What is the revenue of RELLIES AS?

RELLIES AS had revenue of NOK 618,000 in 2025.

Who is the general manager of RELLIES AS?

Nanette Aleksandria Andersen Sørenbye is registered as general manager of RELLIES AS.

Where is RELLIES AS based?

RELLIES AS has its business address in Fornebu.

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.