BIZTRAC BETA
Rental and operating of own or leased real estate

FORMAT INVEST EIENDOM AS

Org. no. 913015517 Limited company (AS) Bjørnafjorden Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 460,000
Operating profit NOK 286,000
Equity NOK 598,000
Incorporated 2013
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.

FORMAT INVEST EIENDOM AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 913015517. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i og utleie av fast eiendom samt det som naturlig følger av dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 460,000 in revenue and NOK 286,000 in operating profit.

Key figures · 2025

Revenue
NOK 460,000
Operating profit
NOK 286,000
Equity
NOK 598,000
Est. value
NOK 899,000

Financial health · 2025

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

Who owns FORMAT INVEST EIENDOM AS?

OS TAXI AS
FORMAT INVEST EIENDOM AS
NOK 460,000 rev. · NOK 286,000 profit

FORMAT INVEST EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FORMAT INVEST EIENDOM AS

Who owns FORMAT INVEST EIENDOM AS?

OS TAXI AS is the largest registered owner, with 100.0%.

What is the revenue of FORMAT INVEST EIENDOM AS?

FORMAT INVEST EIENDOM AS had revenue of NOK 460,000 in 2025.

Where is FORMAT INVEST EIENDOM AS based?

FORMAT INVEST EIENDOM AS has its business address in Os.

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.