BIZTRAC BETA
Collection of non-hazardous waste

J ALMAAS TRANSPORT AS

Org. no. 975807525 Limited company (AS) Høylandet Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK −2.4m
Equity NOK 1.8m
Incorporated 1995
Share capital NOK 123,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,4 mill kr).

J ALMAAS TRANSPORT AS is registered as a limited company in Høylandet, Trøndelag with organisation number 975807525. The business is classified under collection of non-hazardous waste (NACE 38.110). The company was incorporated in 1995. Registered share capital is NOK 123,000, divided into 50 shares. The company's stated purpose is: “Renovasjon samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK −2.4m in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK −2.4m
Equity
NOK 1.8m
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns J ALMAAS TRANSPORT AS?

KRISTIN LONMO ALMAAS
J ALMAAS TRANSPORT AS
NOK 3.6m rev. · NOK −2.4m profit

J ALMAAS TRANSPORT AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about J ALMAAS TRANSPORT AS

Who owns J ALMAAS TRANSPORT AS?

KRISTIN LONMO ALMAAS is the largest registered owner, with 28.0%.

What is the revenue of J ALMAAS TRANSPORT AS?

J ALMAAS TRANSPORT AS had revenue of NOK 3.6m in 2025.

Who is the general manager of J ALMAAS TRANSPORT AS?

Thomas Almaas is registered as general manager of J ALMAAS TRANSPORT AS.

Where is J ALMAAS TRANSPORT AS based?

J ALMAAS TRANSPORT AS has its business address in Høylandet.

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.