BIZTRAC BETA
Manufacture of other food products n.e.c.

JULANTA AS

Org. no. 930827037 Limited company (AS) Grong Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −105,000
Equity NOK 106,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−105k kr).

JULANTA AS is registered as a limited company in Grong, Trøndelag with organisation number 930827037. The business is classified under manufacture of other food products n.e.c. (NACE 10.890). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av alle typer naturlige vekster, helsekost, andre produkter, opplevelser og tjenester tilknyttet dette. Utvikling, utvinning og produksjon av naturprodukter, med tilknyttede behandlinger og tjenester for salg.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −105,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −105,000
Equity
NOK 106,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns JULANTA AS?

LEKSÅS INVEST AS
JULANTA AS
NOK 2.1m rev. · NOK −105,000 profit

JULANTA AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about JULANTA AS

Who owns JULANTA AS?

LEKSÅS INVEST AS is the largest registered owner, with 52.0%.

What is the revenue of JULANTA AS?

JULANTA AS had revenue of NOK 2.1m in 2024.

Who is the general manager of JULANTA AS?

Trond-Gøran Grande Knudsen is registered as general manager of JULANTA AS.

Where is JULANTA AS based?

JULANTA AS has its business address in Grong.

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.