biztrac. BETA
COMPANY REGISTER PROFILE
921995318 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

RAMNÆS CONSULTING AS

Org. no. 921995318 Limited company (AS) Nordre Follo Incorporated 2018 Active
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 0
Incorporated 2018
Share capital NOK 30,000

RAMNÆS CONSULTING AS is registered as a limited company in Nordre Follo, Akershus with organisation number 921995318. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulentvirksomhet tilknyttet informasjonsteknologi.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 0
▼ −100 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns RAMNÆS CONSULTING AS?

RAMNÆS CONSULTING AS
NOK 0 rev. · NOK 0 profit

RAMNÆS CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RAMNÆS CONSULTING AS own?

RAMNÆS CONSULTING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RAMNÆS CONSULTING AS

Who owns RAMNÆS CONSULTING AS?

Jørn Ramnæs is the largest registered owner, with 100.0%.

What is the revenue of RAMNÆS CONSULTING AS?

RAMNÆS CONSULTING AS had revenue of NOK 0 in 2025.

Where is RAMNÆS CONSULTING AS based?

RAMNÆS CONSULTING AS has its business address in Langhus.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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