BIZTRAC BETA
Rental and operating of own or leased real estate

FLATÅSEN BUTIKKEIENDOM AS

Org. no. 987578742 Limited company (AS) Trondheim Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 1.8m
Equity NOK 2.6m
Incorporated 2004
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.

FLATÅSEN BUTIKKEIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 987578742. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, utleie av fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 1.8m
Equity
NOK 2.6m
Est. value
NOK 5.3m

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.2%
Good
Equity as a share of total capital

Who owns FLATÅSEN BUTIKKEIENDOM AS?

GIBOR AS
FLATÅSEN BUTIKKEIENDOM AS
NOK 2.4m rev. · NOK 1.8m profit

FLATÅSEN BUTIKKEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLATÅSEN BUTIKKEIENDOM AS

Who owns FLATÅSEN BUTIKKEIENDOM AS?

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

What is the revenue of FLATÅSEN BUTIKKEIENDOM AS?

FLATÅSEN BUTIKKEIENDOM AS had revenue of NOK 2.4m in 2025.

Where is FLATÅSEN BUTIKKEIENDOM AS based?

FLATÅSEN BUTIKKEIENDOM AS has its business address in Flatåsen.

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.