BIZTRAC BETA
Construction of other civil engineering projects n.e.c.

LEON MUR OG PUSS AS

Org. no. 997849337 Limited company (AS) Ås Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 217,000
Equity NOK 430,000
Incorporated 2012
Share capital NOK 30,000

LEON MUR OG PUSS AS is registered as a limited company in Ås, Akershus with organisation number 997849337. The business is classified under construction of other civil engineering projects n.e.c. (NACE 42.990). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Selskapets virksomhet er mur, puss og flislegging i bygg og anleggsbransjen, samt andre produkter/ tjenester som naturlig hører sammen med dette, herunder også tjenester innen renholds bransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 217,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 217,000
Equity
NOK 430,000
Est. value
NOK 850,000

Financial health · 2025

Liquidity
1.53
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.8%
Good
Equity as a share of total capital

Who owns LEON MUR OG PUSS AS?

INDRIT VRANICI
LEON MUR OG PUSS AS
NOK 2.0m rev. · NOK 217,000 profit

LEON MUR OG PUSS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEON MUR OG PUSS AS

Who owns LEON MUR OG PUSS AS?

INDRIT VRANICI is the largest registered owner, with 48.0%.

What is the revenue of LEON MUR OG PUSS AS?

LEON MUR OG PUSS AS had revenue of NOK 2.0m in 2025.

Who is the general manager of LEON MUR OG PUSS AS?

Xhevdet Tahirukaj is registered as general manager of LEON MUR OG PUSS AS.

Where is LEON MUR OG PUSS AS based?

LEON MUR OG PUSS AS has its business address in Vinterbro.

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.