biztrac. BETA
COMPANY REGISTER PROFILE
935934575 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

RAM'S INVEST AS

Org. no. 935934575 Limited company (AS) Ullensaker Incorporated 2025 Active
Ownership graph ↗
Equity NOK 24,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RAM'S INVEST AS is registered as a limited company in Ullensaker, Akershus with organisation number 935934575. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Equity
NOK 24,000
Est. value
NOK 31,000

Financial health · 2025

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

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

Who owns RAM'S INVEST AS?

RAM'S INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RAM'S INVEST AS own?

RAM'S INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RAM'S INVEST AS

Who owns RAM'S INVEST AS?

Nitesh Kumar Bhardwaj is the largest registered owner, with 100.0%.

Who is the general manager of RAM'S INVEST AS?

Nitesh Kumar Bhardwaj is registered as general manager of RAM'S INVEST AS.

Where is RAM'S INVEST AS based?

RAM'S INVEST AS has its business address in Kløfta.

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.