these symbols cant be used for labels, they have special use.
i dont understand some of them, let me count what i know.

+ ADD
- SUB
/ DIV
* MUL
= EQU
[] value of
, separate registers and other stuff
| logical OR
& logical AND

if someone can till me the uses of these, thanks.

<> less and greater and other stuff that i dont know
: label and other stuff that i dont know
() i dont know
{} i dont know
~ i dont know
# i dont know
` i dont know

<> are also used for grouping symbols in in checks (see chapter 2.2.2 in FASM.pdf) and for passing stuff containing commas to macroinstructions (see chapter 2.3.3 in FASM.pdf). Although, I guess, these cases are technically the same case.

: lets you specify starting offset in file directive (1.2.2), separates segment number and offset in fully-qualified addresses (see examples in 2.1.6, 2.1.8, and it’s a commonly used notation), specifies the base counter value for rept directive (2.3.5), is used as a delimiter for some standard macros (say, proc macro, see 3.1.3). Double colon is also used in addressing space labels (2.2.4).

() override operator precedence in expressions (see numerous examples throughout FASM.pdf), group values for dup operator (1.2.2).

{} enclose macro bodies (2.3.3).
~ means logical negation (2.2.2).
# concatenates operands in macros (2.3.3).
` converts operands to their string representations in macros (2.3.3).

thanks for the details.

1more confusing question:
i do use labels that starts with 1 dot, however i couldnt understand what double dots mean?
technically?

let suppose that in fasm internally exist label "." - root label for all others (it is hidden from direct access but as any other label it can have descendants).
so we define descendants:
first parent name -"."
than descendant joiner - "."
than name of descendant

See the manual, section 1.2.3:

It’s in FASM.pdf, chapter 1.2.3, but seems to be too between-the-lines. The idea is that there’re global and local labels. A local label is “tied” to the nearest preceding global label (NPGL) thus having two names: short one starting with dot and long one that can be obtained by concatenating the NPGL name with the name of the local label.

Now, sometimes, mostly in macros which generate code that might be placed anywhere, you want to have a global label but don’t want it to break the outer code. That’s where double-dotted labels come in handy. Consider the following example:
Labels .InternalLoop and .EndProc generally have MyProc.InternalLoop and MyProc.EndProc as their full names. But since the macro adds its own label and it’s a global label, their full names become MyProc.InternalLoop and Skip.EndProc respectively while the check after OneMoreProc call tried to jump to MyProc.EndProc. So, the compilation fails.

You might say that for such a macro an anonymous label might be a better idea but it would break code that uses anonymouse labels around the macro. Technically, you could use local label (with one dot) and make its name unique with local directive but that would mean that your namespace would be trashed with local labels randomly attached to global ones.

Double-dotted label lets you define a label that will behave as global one except that local labels will not attach to it i.e. will skip it when looking for NGPL.

this is exactly what i wanted to know, thanks.