BIZTRAC BETA
Computer programming activities

RYFY TECH AS

Org. no. 828192302 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 665,000
Operating profit NOK 16,000
Equity NOK 60,000
Incorporated 2021
Share capital NOK 46,000

RYFY TECH AS is registered as a limited company in Stavanger, Rogaland with organisation number 828192302. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2021. Registered share capital is NOK 46,000, divided into 45570 shares. The company's stated purpose is: “Konsulenttjenester innen informasjonsteknologi, samt drift og utvikling av egne og andre selskapers digitale løsninger. Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 665,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2024

Revenue
NOK 665,000
Operating profit
NOK 16,000
Equity
NOK 60,000
Est. value
NOK 159,000

Financial health · 2024

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

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

Who owns RYFY TECH AS?

MIKAL SANDE
RYFY TECH AS
NOK 665,000 rev. · NOK 16,000 profit

RYFY TECH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RYFY TECH AS

Who owns RYFY TECH AS?

MIKAL SANDE is the largest registered owner, with 100.0%.

What is the revenue of RYFY TECH AS?

RYFY TECH AS had revenue of NOK 665,000 in 2024.

Who is the general manager of RYFY TECH AS?

Mikal Sande is registered as general manager of RYFY TECH AS.

Where is RYFY TECH AS based?

RYFY TECH 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 15.06.2026.

Report a problem

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