BIZTRAC BETA
COMPANY REGISTER PROFILE
984761635 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

JUNI AS

Org. no. 984761635 Limited company (AS) Oslo Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 18,000
Operating profit NOK −53,000
Equity NOK 2.5m
Incorporated 2002
Share capital NOK 2.5m

Signals

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

JUNI AS is registered as a limited company in Oslo, Oslo with organisation number 984761635. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 2.5m, divided into 2500000 shares. The company's stated purpose is: “Selv gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå investering i og forvaltning av verdipapirer og fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 18,000 in revenue and NOK −53,000 in operating profit.

Key figures · 2025

Revenue
NOK 18,000
Operating profit
NOK −53,000
Equity
NOK 2.5m
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns JUNI AS?

INGE GRØDUM
JUNI AS
NOK 18,000 rev. · NOK −53,000 profit

JUNI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JUNI AS

Who owns JUNI AS?

INGE GRØDUM is the largest registered owner, with 100.0%.

What is the revenue of JUNI AS?

JUNI AS had revenue of NOK 18,000 in 2025.

Who is the general manager of JUNI AS?

Trine-Lise Grødum is registered as general manager of JUNI AS.

Where is JUNI AS based?

JUNI 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.