BIZTRAC BETA
Floor and wall covering

JELSNES FLIS OG BAD AS

Org. no. 918416714 Limited company (AS) Indre Østfold Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 11.3m
Operating profit NOK 49,000
Equity NOK 520,000
Incorporated 2017
Employees 6
Share capital NOK 30,000

JELSNES FLIS OG BAD AS is registered as a limited company in Indre Østfold, Østfold with organisation number 918416714. The business is classified under floor and wall covering (NACE 43.330). The company was incorporated in 2017 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Bygg og anlegg med hovedfokus på å totalrenovere våtrom. Selskapet kan også investere i andre selskaper, samt i fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.3m in revenue and NOK 49,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.3m
Operating profit
NOK 49,000
Equity
NOK 520,000
Est. value
NOK 365,000

Financial health · 2025

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

Who owns JELSNES FLIS OG BAD AS?

JOACHIM HOLM JELSNES
JELSNES FLIS OG BAD AS
NOK 11.3m rev. · NOK 49,000 profit

JELSNES FLIS OG BAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JELSNES FLIS OG BAD AS

Who owns JELSNES FLIS OG BAD AS?

JOACHIM HOLM JELSNES is the largest registered owner, with 100.0%.

What is the revenue of JELSNES FLIS OG BAD AS?

JELSNES FLIS OG BAD AS had revenue of NOK 11.3m in 2025.

Who is the general manager of JELSNES FLIS OG BAD AS?

Joachim Holm Jelsnes is registered as general manager of JELSNES FLIS OG BAD AS.

Where is JELSNES FLIS OG BAD AS based?

JELSNES FLIS OG BAD AS has its business address in Mysen.

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.