BIZTRAC BETA
Roofing activities

MEMBRANTAK SERVICE AS

Org. no. 932267101 Limited company (AS) Midtre Gauldal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 13.9m
Operating profit NOK 3.9m
Equity NOK 2.0m
Incorporated 2023
Share capital NOK 100,000

MEMBRANTAK SERVICE AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 932267101. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Taktekking, restaurering og reparasjoner av bygg og anlegg samt alt som står i forbindelse med dette. Drive rådgivning og takst innen samme fagfelt, samt deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.9m in revenue and NOK 3.9m in operating profit.

Key figures · 2025

Revenue
NOK 13.9m
Operating profit
NOK 3.9m
Equity
NOK 2.0m
Est. value
NOK 12.0m

Financial health · 2025

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

Who owns MEMBRANTAK SERVICE AS?

MEMBRANTAK HOLDING AS
MEMBRANTAK SERVICE AS
NOK 13.9m rev. · NOK 3.9m profit

MEMBRANTAK SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MEMBRANTAK SERVICE AS

Who owns MEMBRANTAK SERVICE AS?

MEMBRANTAK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MEMBRANTAK SERVICE AS?

MEMBRANTAK SERVICE AS had revenue of NOK 13.9m in 2025.

Who is the general manager of MEMBRANTAK SERVICE AS?

Hans Ivar Brattset is registered as general manager of MEMBRANTAK SERVICE AS.

Where is MEMBRANTAK SERVICE AS based?

MEMBRANTAK SERVICE AS has its business address in Støren.

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.