BIZTRAC BETA
Masonry and bricklaying activities

FLIS- OG MURSERVICE AS

Org. no. 992436492 Limited company (AS) Levanger Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 8.7m
Operating profit NOK 308,000
Equity NOK 776,000
Incorporated 2008
Employees 8
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FLIS- OG MURSERVICE AS is registered as a limited company in Levanger, Trøndelag with organisation number 992436492. The business is classified under masonry and bricklaying activities (NACE 43.910). The company was incorporated in 2008 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av tjenester og handelsvarer samt deltagelse i selskaper av samme eller annen art gjennom aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.7m in revenue and NOK 308,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.7m
Operating profit
NOK 308,000
Equity
NOK 776,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns FLIS- OG MURSERVICE AS?

LFM AS
FLIS- OG MURSERVICE AS
NOK 8.7m rev. · NOK 308,000 profit

FLIS- OG MURSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLIS- OG MURSERVICE AS

Who owns FLIS- OG MURSERVICE AS?

LFM AS is the largest registered owner, with 100.0%.

What is the revenue of FLIS- OG MURSERVICE AS?

FLIS- OG MURSERVICE AS had revenue of NOK 8.7m in 2025.

Where is FLIS- OG MURSERVICE AS based?

FLIS- OG MURSERVICE AS has its business address in Levanger.

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.