BIZTRAC BETA
Architectural activities

RÅKKENRÅLL AS

Org. no. 967196134 Limited company (AS) Oslo Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 31,000
Operating profit NOK −211,000
Equity NOK 14,000
Incorporated 1993
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−211k kr).

RÅKKENRÅLL AS is registered as a limited company in Oslo, Oslo with organisation number 967196134. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 1993. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å utvikle fremtidsrettet arkitektur og design med fokus på estetikk, tradisjon og bærekraft.”. The most recent filed accounts, for the 2025 financial year, show NOK 31,000 in revenue and NOK −211,000 in operating profit.

Key figures · 2025

Revenue
NOK 31,000
Operating profit
NOK −211,000
Equity
NOK 14,000
Est. value
NOK 22,000

Financial health · 2025

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

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

Who owns RÅKKENRÅLL AS?

PEDINCO AS
RÅKKENRÅLL AS
NOK 31,000 rev. · NOK −211,000 profit

RÅKKENRÅLL AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RÅKKENRÅLL AS er morselskap for 1 datterselskap:

Frequently asked questions about RÅKKENRÅLL AS

Who owns RÅKKENRÅLL AS?

PEDINCO AS is the largest registered owner, with 100.0%.

What is the revenue of RÅKKENRÅLL AS?

RÅKKENRÅLL AS had revenue of NOK 31,000 in 2025.

Who is the general manager of RÅKKENRÅLL AS?

Peder Fossum Ulven is registered as general manager of RÅKKENRÅLL AS.

Where is RÅKKENRÅLL AS based?

RÅKKENRÅLL 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.