BIZTRAC BETA
Plumbing installation

FLATANGER RØR AS

Org. no. 926789252 Limited company (AS) Flatanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK −95,000
Equity NOK −309,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−309k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−95k kr).

FLATANGER RØR AS is registered as a limited company in Flatanger, Trøndelag with organisation number 926789252. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rørleggerarbeid og salg av varer og tjenester. ”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK −95,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK −95,000
Equity
NOK −309,000

Financial health · 2024

Liquidity
0.38
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-79.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FLATANGER RØR AS?

IVER AUNE KROGSTAD
FLATANGER RØR AS
NOK 1.0m rev. · NOK −95,000 profit

FLATANGER RØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLATANGER RØR AS

Who owns FLATANGER RØR AS?

IVER AUNE KROGSTAD is the largest registered owner, with 100.0%.

What is the revenue of FLATANGER RØR AS?

FLATANGER RØR AS had revenue of NOK 1.0m in 2024.

Who is the general manager of FLATANGER RØR AS?

Iver Aune Krogstad is registered as general manager of FLATANGER RØR AS.

Where is FLATANGER RØR AS based?

FLATANGER RØR AS has its business address in Flatanger.

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.