BIZTRAC BETA
Work training and permanently adapted work

LEVA-FRO AS

Org. no. 964417210 Limited company (AS) Levanger Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 29.2m
Operating profit NOK −642,000
Equity NOK 3.1m
Incorporated 1992
Employees 25
Share capital NOK 238,000

Signals

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

LEVA-FRO AS is registered as a limited company in Levanger, Trøndelag with organisation number 964417210. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 1992 and has 25 registered employees. Registered share capital is NOK 238,000, divided into 100 shares. The company's stated purpose is: “Leva-Fro er en fremtidsrettet bedrift som brenner for å skape muligheter for alle. Med solid kompetanse innen arbeidsinkludering bidrar vi i tett samarbeid andre aktører til å finne løsninger som gjør en forskjell både for enkeltmennesker og for samfunnet.”. The most recent filed accounts, for the 2025 financial year, show NOK 29.2m in revenue and NOK −642,000 in operating profit.

Key figures · 2025

Revenue
NOK 29.2m
Operating profit
NOK −642,000
Equity
NOK 3.1m
Est. value
NOK 25.6m

Financial health · 2025

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

Who owns LEVA-FRO AS?

No shareholders are registered for LEVA-FRO AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LEVA-FRO AS

What is the revenue of LEVA-FRO AS?

LEVA-FRO AS had revenue of NOK 29.2m in 2025.

Who is the general manager of LEVA-FRO AS?

Rune Lyngen is registered as general manager of LEVA-FRO AS.

Where is LEVA-FRO AS based?

LEVA-FRO AS has its business address in Levanger.

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.