BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER STIG LYSVAND AS

Org. no. 911639580 Limited company (AS) Indre Fosen Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 148,000
Equity NOK 2.3m
Incorporated 2013
Share capital NOK 30,000

BYGGMESTER STIG LYSVAND AS is registered as a limited company in Indre Fosen, Trøndelag with organisation number 911639580. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Entreprenør- og servicevirksomhet, og annen økonomisk virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 148,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 148,000
Equity
NOK 2.3m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns BYGGMESTER STIG LYSVAND AS?

STIG LYSVAND
BYGGMESTER STIG LYSVAND AS
NOK 3.5m rev. · NOK 148,000 profit

BYGGMESTER STIG LYSVAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER STIG LYSVAND AS

Who owns BYGGMESTER STIG LYSVAND AS?

STIG LYSVAND is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER STIG LYSVAND AS?

BYGGMESTER STIG LYSVAND AS had revenue of NOK 3.5m in 2025.

Who is the general manager of BYGGMESTER STIG LYSVAND AS?

Stig Lysvand is registered as general manager of BYGGMESTER STIG LYSVAND AS.

Where is BYGGMESTER STIG LYSVAND AS based?

BYGGMESTER STIG LYSVAND AS has its business address in Leksvik.

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.