BIZTRAC BETA
Retail sale of pleasure boats and equipment

BLINDLEIA AS

Org. no. 996844293 Limited company (AS) Lillesand Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 15,000
Equity NOK 5.3m
Incorporated 2011
Share capital NOK 100,000

BLINDLEIA AS is registered as a limited company in Lillesand, Agder with organisation number 996844293. The business is classified under retail sale of pleasure boats and equipment (NACE 47.632). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, reparasjon, vedlikehold av båter, motorer og motorkjøretøy, vaktmestertjenester, samt annen virksomhet som naturlig faller inn under dette. Selskapet kan også drive med investeringer i bl.a. eiendom, utstyr, annen nærinsgsvirksomhet og selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 15,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 15,000
Equity
NOK 5.3m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns BLINDLEIA AS?

HÅVARD KJELSRUD MATHISEN
BLINDLEIA AS
NOK 1.5m rev. · NOK 15,000 profit

BLINDLEIA AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BLINDLEIA AS own?

BLINDLEIA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLINDLEIA AS

Who owns BLINDLEIA AS?

HÅVARD KJELSRUD MATHISEN is the largest registered owner, with 90.0%.

What is the revenue of BLINDLEIA AS?

BLINDLEIA AS had revenue of NOK 1.5m in 2025.

Where is BLINDLEIA AS based?

BLINDLEIA AS has its business address in Høvåg.

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.