BIZTRAC BETA
Other technical consultancy

RAMBO CONSULTING AS

Org. no. 922077827 Limited company (AS) Porsgrunn Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 272,000
Equity NOK 982,000
Incorporated 2018
Share capital NOK 30,000

RAMBO CONSULTING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 922077827. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Rådgiving, utleie av personal, investering og eventuelt annet selskapet vil satse på.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 272,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 272,000
Equity
NOK 982,000
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
1.76
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
47.3%
Very good
Equity as a share of total capital

Who owns RAMBO CONSULTING AS?

STIAN RAMBO PEDERSEN
RAMBO CONSULTING AS
NOK 2.7m rev. · NOK 272,000 profit

RAMBO CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RAMBO CONSULTING AS own?

RAMBO CONSULTING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RAMBO CONSULTING AS

Who owns RAMBO CONSULTING AS?

STIAN RAMBO PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of RAMBO CONSULTING AS?

RAMBO CONSULTING AS had revenue of NOK 2.7m in 2025.

Who is the general manager of RAMBO CONSULTING AS?

Stian Rambo Pedersen is registered as general manager of RAMBO CONSULTING AS.

Where is RAMBO CONSULTING AS based?

RAMBO CONSULTING AS has its business address in Porsgrunn.

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.