BIZTRAC BETA
Joinery installation

RYDDESERVICE AS

Org. no. 913430859 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 284,000
Operating profit NOK 73,000
Equity NOK 392,000
Incorporated 2014
Share capital NOK 30,000

RYDDESERVICE AS is registered as a limited company in Oslo, Oslo with organisation number 913430859. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Demontering og montering av innredninger, møbler etc og søppelhåndtering, maling etc service, videresalg av hvitevarer med tilhørende transport.”. The most recent filed accounts, for the 2025 financial year, show NOK 284,000 in revenue and NOK 73,000 in operating profit.

Key figures · 2025

Revenue
NOK 284,000
Operating profit
NOK 73,000
Equity
NOK 392,000
Est. value
NOK 349,000

Financial health · 2025

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

Who owns RYDDESERVICE AS?

DAVID MIKAEL ABRAHAMSSON
RYDDESERVICE AS
NOK 284,000 rev. · NOK 73,000 profit

RYDDESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RYDDESERVICE AS own?

RYDDESERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RYDDESERVICE AS

Who owns RYDDESERVICE AS?

DAVID MIKAEL ABRAHAMSSON is the largest registered owner, with 100.0%.

What is the revenue of RYDDESERVICE AS?

RYDDESERVICE AS had revenue of NOK 284,000 in 2025.

Who is the general manager of RYDDESERVICE AS?

David Mikael Abrahamsson is registered as general manager of RYDDESERVICE AS.

Where is RYDDESERVICE AS based?

RYDDESERVICE 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 15.06.2026.

Report a problem

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