BIZTRAC BETA
Rental and operating of own or leased real estate

LERVÅG AS

Org. no. 947557246 Limited company (AS) Hitra Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK −115,000
Equity NOK 4,000
Incorporated 1988
Share capital NOK 300,000

Signals

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

LERVÅG AS is registered as a limited company in Hitra, Trøndelag with organisation number 947557246. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1988. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Entreprenørvirksomhet, eie eiendom og drive utleie av disse, salg og kjøp av disse varer og tjenester samt alt som hører dertil, samt å delta i andre foretagender. ”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK −115,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK −115,000
Equity
NOK 4,000
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.6%
Weak
Equity as a share of total capital

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

Who owns LERVÅG AS?

STIG ATLE LERVÅG
LERVÅG AS
NOK 2.2m rev. · NOK −115,000 profit

LERVÅG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LERVÅG AS

Who owns LERVÅG AS?

STIG ATLE LERVÅG is the largest registered owner, with 100.0%.

What is the revenue of LERVÅG AS?

LERVÅG AS had revenue of NOK 2.2m in 2024.

Who is the general manager of LERVÅG AS?

Stig Atle Lervåg is registered as general manager of LERVÅG AS.

Where is LERVÅG AS based?

LERVÅG AS has its business address in Sandstad.

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.