BIZTRAC BETA
COMPANY REGISTER PROFILE
976253183 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other technical consultancy

KOSAS AS

Org. no. 976253183 Limited company (AS) Frogn Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 81,000
Operating profit NOK 22,000
Equity NOK 653,000
Incorporated 1996
Share capital NOK 320,000

KOSAS AS is registered as a limited company in Frogn, Akershus with organisation number 976253183. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 1996. Registered share capital is NOK 320,000, divided into 3200 shares. The company's stated purpose is: “Salg av profesjonelle tjenester innen utforskning og produksjon av hydrokarboner og relaterte områder til den norske og internasjonale oljeindustrien. Import, markedsføring og salg av varer innen møblering og interiør. Konsulentvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 81,000 in revenue and NOK 22,000 in operating profit.

Key figures · 2024

Revenue
NOK 81,000
Operating profit
NOK 22,000
Equity
NOK 653,000
Est. value
NOK 403,000

Financial health · 2024

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

Who owns KOSAS AS?

GEIR KRISTIAN YTRELAND
KOSAS AS
NOK 81,000 rev. · NOK 22,000 profit

KOSAS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOSAS AS

Who owns KOSAS AS?

GEIR KRISTIAN YTRELAND is the largest registered owner, with 100.0%.

What is the revenue of KOSAS AS?

KOSAS AS had revenue of NOK 81,000 in 2024.

Who is the general manager of KOSAS AS?

Patricia Elena Ytreland-Tarczay is registered as general manager of KOSAS AS.

Where is KOSAS AS based?

KOSAS AS has its business address in Drøbak.

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.