BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

JUNIOR CONSULTING AS

Org. no. 998354730 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 1,000
Equity NOK 58,000
Incorporated 2012
Share capital NOK 30,000

JUNIOR CONSULTING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 998354730. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Salg av konsulenttjenester fra studenter ved NTNU til næringslivet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 1,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 1,000
Equity
NOK 58,000
Est. value
NOK 34,000

Financial health · 2024

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

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

Who owns JUNIOR CONSULTING AS?

SARA KRISTINA HARNESHAUG
JUNIOR CONSULTING AS
NOK 3.0m rev. · NOK 1,000 profit

JUNIOR CONSULTING AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about JUNIOR CONSULTING AS

Who owns JUNIOR CONSULTING AS?

SARA KRISTINA HARNESHAUG is the largest registered owner, with 20.0%.

What is the revenue of JUNIOR CONSULTING AS?

JUNIOR CONSULTING AS had revenue of NOK 3.0m in 2024.

Who is the general manager of JUNIOR CONSULTING AS?

Andreas Urne is registered as general manager of JUNIOR CONSULTING AS.

Where is JUNIOR CONSULTING AS based?

JUNIOR CONSULTING AS has its business address in Trondheim.

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.