BIZTRAC BETA
Construction of residential and non-residential buildings

LEIRVIK-BYGG AS

Org. no. 993347779 Limited company (AS) Farsund Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 54,000
Equity NOK 379,000
Incorporated 2008
Share capital NOK 100,000

LEIRVIK-BYGG AS is registered as a limited company in Farsund, Agder with organisation number 993347779. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Snekkervirksomhet, eiendomsutvikling, kjøp, salg, utleie av tomter og fast eiendom samt alt hva dermed står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 54,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 54,000
Equity
NOK 379,000
Est. value
NOK 348,000

Financial health · 2024

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

Who owns LEIRVIK-BYGG AS?

ØYVIND LEIRVIK
LEIRVIK-BYGG AS
NOK 2.0m rev. · NOK 54,000 profit

LEIRVIK-BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEIRVIK-BYGG AS

Who owns LEIRVIK-BYGG AS?

ØYVIND LEIRVIK is the largest registered owner, with 100.0%.

What is the revenue of LEIRVIK-BYGG AS?

LEIRVIK-BYGG AS had revenue of NOK 2.0m in 2024.

Who is the general manager of LEIRVIK-BYGG AS?

Øyvind Leirvik is registered as general manager of LEIRVIK-BYGG AS.

Where is LEIRVIK-BYGG AS based?

LEIRVIK-BYGG AS has its business address in Vanse.

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.