BIZTRAC BETA
Other technical consultancy

LOGOS CAPITAL AS

Org. no. 918486690 Limited company (AS) Herøy Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 2.5m
Equity NOK 5.0m
Incorporated 2017
Share capital NOK 51,000

LOGOS CAPITAL AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 918486690. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 51,000, divided into 3000 shares. The company's stated purpose is: “Å investere i eiendom, aksjer og andre selskaper og dertil tilhørende tjenester, samt teknisk konsulentvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 2.5m
Equity
NOK 5.0m
Est. value
NOK 11.4m

Financial health · 2024

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

Who owns LOGOS CAPITAL AS?

JON INGE FYLLING MOLTU
LOGOS CAPITAL AS
NOK 2.7m rev. · NOK 2.5m profit

LOGOS CAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LOGOS CAPITAL AS own?

LOGOS CAPITAL AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LOGOS CAPITAL AS

Who owns LOGOS CAPITAL AS?

JON INGE FYLLING MOLTU is the largest registered owner, with 100.0%.

What is the revenue of LOGOS CAPITAL AS?

LOGOS CAPITAL AS had revenue of NOK 2.7m in 2024.

Who is the general manager of LOGOS CAPITAL AS?

Jon Inge Fylling Moltu is registered as general manager of LOGOS CAPITAL AS.

Where is LOGOS CAPITAL AS based?

LOGOS CAPITAL AS has its business address in Fosnavåg.

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.