BIZTRAC BETA
Rental and operating of own or leased real estate

FLATÅS BYGG AS

Org. no. 921143257 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 531,000
Operating profit NOK −371,000
Equity NOK 9.7m
Incorporated 2018
Share capital NOK 60,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−371k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FLATÅS BYGG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921143257. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 60,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av fast eiendom, samt ved aksjetegning eller på andre måter delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 531,000 in revenue and NOK −371,000 in operating profit.

Key figures · 2025

Revenue
NOK 531,000
Operating profit
NOK −371,000
Equity
NOK 9.7m
Est. value
NOK 7.4m

Financial health · 2025

Liquidity
66.19
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.8%
Very good
Equity as a share of total capital

Who owns FLATÅS BYGG AS?

NORINVEST AS
FLATÅS BYGG AS
NOK 531,000 rev. · NOK −371,000 profit

FLATÅS BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLATÅS BYGG AS

Who owns FLATÅS BYGG AS?

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

What is the revenue of FLATÅS BYGG AS?

FLATÅS BYGG AS had revenue of NOK 531,000 in 2025.

Where is FLATÅS BYGG AS based?

FLATÅS BYGG AS has its business address in Trondheim.

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.